Comment by esafak
4 days ago
By not using a server as an interface, UTCP more tightly couples the caller to the tool. For example, a search MCP server could make the search provider an optional parameter to be dynamically selected without breaking the contract. With UTCP you can not do that.
Given that tool calling usually does not constitute the bulk of a typical LLM query's time, I think optimizing the latency by eliminating the interface is an unwise architectural choice. Interfaces are good things.
It's not about latency. It's about security and rebuilding existing infrastructure. There are plenty of communication protocols to get anything you can imagine done on the internet. We should use those and write our interfaces and wrappers using those, not MCP. That is what UTCP does. It allows agents to use existing infra, communication protocols and security.