tadata-org
Support for MCP Resources alongside Tools
The current implementation only supports Tools, which are meant for actions with computation and side effects. However, MCP also defines Resources - a way to expose data to LLMs without significant computation or side effects (similar to GET endpoints in REST APIs). The distinction between these two concepts is important for API design and LLM interaction patterns.
maybe to Add support for Resources alongside existing Tool functionality, allowing the server to distinguish between data-providing endpoints (Resources) and action-performing endpoints (Tools). This would align the implementation with the complete MCP specification.
alternatives Using Tools for everything, but this doesn't properly represent the semantic difference between data retrieval and action execution, potentially leading to less clear API designs.
Hi @reubinoff-prime , I definitely agree. Need to think how to implement such enhancement, if by manually specifying which are tools and which are resources, or by auto-detection based of the endpoint type? Also worth noting that client support in resources is still somewhat limited. Very open to hold a discussion here and see more contributions!
