Skip to content

Conversation

dak2
Copy link
Contributor

@dak2 dak2 commented Oct 13, 2025

Motivation and Context

Follow up: #160

How Has This Been Tested?

Check existing and added test cases for this case in test/mcp/client_test.rb

Breaking Changes

None

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

- Add test for empty tools array response to ensure client handles empty
  results correctly
- Update call_tool test to use proper content format (array of content
  objects) instead of plain string based on
  modelcontextprotocol spec.
  https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/docs/specification/2025-03-26/server/tools.mdx#calling-tools

Follow up: modelcontextprotocol#160
@koic koic merged commit f8557e5 into modelcontextprotocol:main Oct 13, 2025
5 checks passed
@dak2 dak2 deleted the fix-client-tools-test branch October 13, 2025 23:14
@topherbullock topherbullock mentioned this pull request Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants