step 6 update
This commit is contained in:
@@ -23,6 +23,21 @@ Normative conclusions from those sources:
|
|||||||
3. Resources and tools must resolve to the same canonical authored markdown.
|
3. Resources and tools must resolve to the same canonical authored markdown.
|
||||||
4. Fallback behavior should keep context bounded and deterministic.
|
4. Fallback behavior should keep context bounded and deterministic.
|
||||||
|
|
||||||
|
### FastMCP Source Baseline (Authoritative References)
|
||||||
|
|
||||||
|
Step 6 fallback behavior and compatibility-layer expectations align with:
|
||||||
|
|
||||||
|
1. [FastMCP server concepts](https://gofastmcp.com/servers/server)
|
||||||
|
2. [FastMCP resources and resource templates](https://gofastmcp.com/servers/resources)
|
||||||
|
3. [FastMCP resources-as-tools transform](https://gofastmcp.com/servers/transforms/resources-as-tools)
|
||||||
|
4. [MCP specification: resources](https://modelcontextprotocol.io/specification/latest/server/resources)
|
||||||
|
|
||||||
|
Applied conclusions for this step:
|
||||||
|
|
||||||
|
1. Resource contracts remain canonical and should be surfaced directly when clients support resource attachment.
|
||||||
|
2. Tool-first compatibility layers should wrap canonical resource reads rather than creating alternate authored-content stores.
|
||||||
|
3. URI-template-backed resource identity remains stable across direct-resource and tool-compatibility access paths.
|
||||||
|
|
||||||
### Discovery Priority Contract (Normative)
|
### Discovery Priority Contract (Normative)
|
||||||
|
|
||||||
Preferred sequence for skill discovery and loading:
|
Preferred sequence for skill discovery and loading:
|
||||||
|
|||||||
Reference in New Issue
Block a user