21 pointsby arnav317 hours ago3 comments
  • rambo12317 hours ago
    Why not let MCP do this? I agree MCP fundamentally has limitations, curious if MCP would be able to cover this
    • arnav317 hours ago
      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
  • beardyw17 hours ago
    Honestly, what problem is this solving?
    • arnav316 hours ago
      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.
      • beardyw16 hours ago
        Thank you for your reply. But my question was more about what real life problem is being solved. I just don't see it.
        • arnav36 hours ago
          Yes agreed, with the maturity of Agents this is not an immediate problem. In a word, the problem it solves it "automation". Automation of complex tasks which were not possible until now. It's one piece in a large puzzle that we must solve while embracing agents and AI. Do you think this would be valuable? Letting agents book an Uber for you, or order on Amazon, or perform payments and more
  • arnav317 hours ago
    [dead]