MPC inspector checks on replay results are stricter than the specification (or the specification is incorrect)

[symdeb]

Describe the bug

[1] Per the MCP specification the ResultType is now required by 2026-07-28 specification
For inspector this seems not sufficient for a /list call replay, but sufficient for the initial connection.
[2] This behavior is inconsistent
[3] The SEP describes these requirements but the final specification does not include it.
[4] Adding these field works,,except for resources/templates/list that still gets rejected by inspector

2026-07-28 Specification: does NOT specify ttlMs and cacheScope

    "resultType": "complete",
    "tools": [
      {

To Reproduce

1. Connect an MCP server. Do not return ResultType, ttLMs and cacheScope for tools/list
2. inspector connects fine
3. Click on the replay (in the right side of the screen that list the tools)
4. Inspector reports an error that ResultType is required for 2026-07-28
5. Add the resultType "complete"
6. Inspector still rejects
7. Add ttlMs and cacheScope to the result
8. inspector accepts the request (except for resources/templates/list that still gets rejected by inspector)

Additional context
https://modelcontextprotocol.io/specification/2026-07-28/server/tools
https://modelcontextprotocol.io/seps/2549-TTL-for-list-results#sep-2549-ttl-for-list-results

1. Does anyone test anything ?
2. Did anyone review all the SEPs that should match the specification ?
3. As a hobbyist for fun to find these issues is remarkable .