What's broken?
The spec is ambiguous or self-contradictory
Where in the spec or docs?
https://modelcontextprotocol.io/specification/2026-07-28/server/resources#list-changed-notification
What should happen?
The spec should explicitly define what a client/server should do about resource template list changes.
What actually happens?
The spec is ambiguous - it doesn't explicitly say what a client/server should do about resource template list changes.
It could be that:
notifications/resources/list_changed is intended to cover both - resources and resource templates, and clients should re-fetch both lists, or
- Template list changes are simply not covered by the current spec.
Anything else?
No response
What's broken?
The spec is ambiguous or self-contradictory
Where in the spec or docs?
https://modelcontextprotocol.io/specification/2026-07-28/server/resources#list-changed-notification
What should happen?
The spec should explicitly define what a client/server should do about resource template list changes.
What actually happens?
The spec is ambiguous - it doesn't explicitly say what a client/server should do about resource template list changes.
It could be that:
notifications/resources/list_changedis intended to cover both - resources and resource templates, and clients should re-fetch both lists, orAnything else?
No response