1ff5d88370Updates SEP-2549 caching traceability text to match modelcontextprotocol/modelcontextprotocol#2890: - Scope the five *-caching-hints requirements to results with resultType: "complete" (interim input_required results carry no hints). - Add two excluded client MUST NOT rows from the new Cache Key section (cache-key mismatch, multi round-trip retry results). Neither is wire-observable since a conformant client may simply never cache. No check IDs change; traceability.json will be refreshed by the scheduled traceability workflow. Claude-Session: https://claude.ai/code/session_01Gbqx5LodtAghT5fRYFxeja
48 lines
4.3 KiB
YAML
48 lines
4.3 KiB
YAML
sep: 2549
|
|
spec_url: https://modelcontextprotocol.io/specification/draft/server/utilities/caching
|
|
requirements:
|
|
- check: sep-2549-tools-list-caching-hints
|
|
text: 'Servers MUST include caching hints on results with resultType: "complete" returned by tools/list'
|
|
- check: sep-2549-prompts-list-caching-hints
|
|
text: 'Servers MUST include caching hints on results with resultType: "complete" returned by prompts/list'
|
|
- check: sep-2549-resources-list-caching-hints
|
|
text: 'Servers MUST include caching hints on results with resultType: "complete" returned by resources/list'
|
|
- check: sep-2549-resources-templates-list-caching-hints
|
|
text: 'Servers MUST include caching hints on results with resultType: "complete" returned by resources/templates/list'
|
|
- check: sep-2549-resources-read-caching-hints
|
|
text: 'Servers MUST include caching hints on results with resultType: "complete" returned by resources/read'
|
|
- check: sep-2549-ttl-non-negative
|
|
text: 'Servers MUST provide a ttlMs value that is >= 0'
|
|
- check: sep-2549-cache-scope-valid
|
|
text: 'cacheScope indicates the intended scope of the cached response, either "public" or "private"'
|
|
|
|
- text: 'If ttlMs is 0, the response SHOULD be considered immediately stale.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'If ttlMs is positive, the client SHOULD consider the result fresh for that many milliseconds after receiving the response.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'If ttlMs is absent, clients SHOULD assume a default of 0 (immediately stale) and rely on their own caching heuristics or notifications.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'If ttlMs is negative, clients SHOULD ignore it and treat it as 0.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'Once the TTL expires, the response is stale and the client SHOULD re-fetch on next access.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'Clients SHOULD NOT treat TTL as a polling interval that triggers automatic background refetches.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'Implementations that do choose to poll MUST apply jitter and backoff.'
|
|
excluded: 'Client-side polling behavior; not observable at the protocol level'
|
|
- text: 'Cached responses MAY be reused for the same authorization context. Caches MUST NOT be shared across authorization contexts (e.g. a different access token requires a different cache).'
|
|
excluded: 'Client/cache-side behavior; not observable at the protocol level'
|
|
- text: 'When a cached page expires, the client SHOULD re-fetch that page using its cursor.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'Clients that require a consistent snapshot of the full list SHOULD re-fetch from the beginning (without a cursor).'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'If a cursor becomes invalid (e.g., the server returns an error for a previously valid cursor), the client SHOULD discard all cached pages and re-fetch from the beginning.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'Servers MUST be aware that responses with a "public" cacheScope may be shared between callers even if the Result is coming from an authenticated endpoint.'
|
|
excluded: 'Server-side awareness requirement; implementation guidance not testable via protocol messages'
|
|
- text: 'Server implementors MUST apply appropriate per-primitive access controls, and MUST NOT rely on cacheScope alone to prevent unauthorized access to primitives.'
|
|
excluded: 'Server-side access control; implementation guidance not testable via protocol messages'
|
|
- text: 'Clients MUST NOT serve a cached response for a request whose method or parameters differ from the request that produced it.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|
|
- text: 'Results produced by retrying a request through the multi round-trip requests mechanism (requests carrying inputResponses or requestState) MUST NOT be cached.'
|
|
excluded: 'Client-side caching behavior; not observable at the protocol level'
|