| Filename | Latest commit message | Latest commit date |
|---|---|---|
20e4e44509Update server-side tool error handling to return `CallToolResult` with `isError: true` instead of throwing protocol-level exceptions, conforming with MCP specification ## Motivation and Context [The MCP specification states](https://modelcontextprotocol.io/specification/2025-06-18/schema#calltoolresult): > Any errors that originate from the tool SHOULD be reported inside the result object, with isError set to true, not as an MCP protocol-level error response. Otherwise, the LLM would not be able to see that an error occurred and self-correct. This PR updates the kotlin sdk to match this behavior ## How Has This Been Tested? All tests pass successfully with the new behavior ## Breaking Changes None ## Types of changes - [x] 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 - [x] I have read the [MCP Documentation](https://modelcontextprotocol.io) - [x] My code follows the repository's style guidelines - [x] New and existing tests pass locally - [x] I have added appropriate error handling - [x] I have added or updated documentation as needed ## Additional context The TypeScript SDK was recently updated [#1044](https://github.com/modelcontextprotocol/typescript-sdk/pull/1044) to conform with the MCP specification regarding tool error handling. That’s why we got exceptions in the integration tests |
||
| .. | ||
| src | ||
| build.gradle.kts | ||