chore: add more draft specs updates#3566
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces client-side caching support for MCP tools and prompts list results by adding a CacheableResult struct (with TtlMs and CacheScope fields) and embedding it into ListToolsResult and ListPromptsResult. It also updates JSON-RPC error codes and adapts the test suite to assert the new cache fields. The reviewer feedback suggests defining a custom CacheScope type and constants (e.g., CacheScopePublic) instead of using hardcoded string literals to improve type safety and prevent typos across the codebase.
Yuan325
added
the
release candidate
|
Conformance test runner is crashing with a Seems like calling |
|
FYI, to pass the capability enforcement tests, we need to intercept the diagnostic tool |
|
@Yuan325 just to confirm, we're going with a default TTL and CacheScope for conformance for now right? |
|
@dishaprakash Yes, seems like those values are required. But it should still be updated when we eventually implement Groups~ |
|
🧨 Preview deployments removed. Cloudflare Pages environments for |
5 participants
This PR add the following updates to the draft specs:
HeaderMismatch,MissingRequiredClientCapability,UnsupportedProtocolVersion(Define error code allocation policy and renumber draft error codes modelcontextprotocol/modelcontextprotocol#2907)ttlMsandcacheScopevalue in server to fulfill conformance tests: https://modelcontextprotocol.io/seps/2549-TTL-for-list-results#cache-scopeINVALID_PARAMSerror withhttp.StatusBadRequestwhen it's due to _meta