Good point, MCPs are built for high breadth low depth usecases. Concierge is built for high depth low breadth. The agent is not supposed to have context on thousands of APIs or tools
Today MCP is the closest we have for Agents executing business logic. It's very well known MCPs dont scale well beyond 50 tools.
This solves the scale of having 1000+ tools/API calls, and allows service owners to contextualize how these tools must be called, and in what context.
Imagine an Agent ordering for you on Amazon, and it attempts to checkout with no items in the cart.
Concierge ensures that an Agent can call 1000+ APIs/tools extremely reliably, and allows service owners to define how to call the service.
Why not let MCP do this? I agree MCP fundamentally has limitations, curious if MCP would be able to cover this
Good point, MCPs are built for high breadth low depth usecases. Concierge is built for high depth low breadth. The agent is not supposed to have context on thousands of APIs or tools
Honestly, what problem is this solving?
Today MCP is the closest we have for Agents executing business logic. It's very well known MCPs dont scale well beyond 50 tools. This solves the scale of having 1000+ tools/API calls, and allows service owners to contextualize how these tools must be called, and in what context. Imagine an Agent ordering for you on Amazon, and it attempts to checkout with no items in the cart. Concierge ensures that an Agent can call 1000+ APIs/tools extremely reliably, and allows service owners to define how to call the service.
Thank you for your reply. But my question was more about what real life problem is being solved. I just don't see it.
[dead]