I think it is now possible to do one curl to call an MCP tool, instead of three previously.
I tried MCP before but the models still needed a lot of hand-holding to be able to use the MCP tools effectively, and I found that just giving them REST endpoints with good examples and descriptions in the OpenAPI/Swagger docs seems to be a better approach. They can explore the REST endpoints easily with curl to get a hang of them.
You may be able to reduce context usage by having one tool that can leverage multiple API endpoints behind the scenes. This abstraction layer is one of the benefits of MCP.
I think it is now possible to do one curl to call an MCP tool, instead of three previously.
I tried MCP before but the models still needed a lot of hand-holding to be able to use the MCP tools effectively, and I found that just giving them REST endpoints with good examples and descriptions in the OpenAPI/Swagger docs seems to be a better approach. They can explore the REST endpoints easily with curl to get a hang of them.
You may be able to reduce context usage by having one tool that can leverage multiple API endpoints behind the scenes. This abstraction layer is one of the benefits of MCP.