MCP is a lot deeper than just tools. We haven't scratched the surface on what...
View original threadMCP is a lot deeper than just tools. We haven't scratched the surface on what it can do.
@timkellogg.me
i thought i understood resources, but no — they’re to manage caching
you don’t want to duplicate files in the context, and you don’t want to move them around (triggers cache invalidation)
resource URIs are a cache key for figuring out if the resource is in the prompt already
you don’t want to duplicate files in the context, and you don’t want to move them around (triggers cache invalidation)
resource URIs are a cache key for figuring out if the resource is in the prompt already
27
1
prompts:
- while generating a prompt, load new tools and use the returned prompt to instruct how to use them
- use an LLM to format a prompt
- lookup info from a database and pump it into a prompt
- while generating a prompt, load new tools and use the returned prompt to instruct how to use them
- use an LLM to format a prompt
- lookup info from a database and pump it into a prompt
3
resources:
- tool accepts a resource URI (e.g. a DB record)
- tool returns 3 URIs
- prompt references URIs (e.g. a base directory to work from)
- proactive pushing resources (always do this if compatibility is important)
- reactive pulling resources (do this if network bandwidth is important)
- tool accepts a resource URI (e.g. a DB record)
- tool returns 3 URIs
- prompt references URIs (e.g. a base directory to work from)
- proactive pushing resources (always do this if compatibility is important)
- reactive pulling resources (do this if network bandwidth is important)
3
notifications:
- change list of active tools (only add pls) during any server-side op
- status updates for long operations
logging:
- standard logger interface, client responsible for handling
- change list of active tools (only add pls) during any server-side op
- status updates for long operations
logging:
- standard logger interface, client responsible for handling
2