razvi0211

5 ms·

1.
by razvi0211 1y ago
UTCP is a rule-based deterministic protocol for tool calling. No AI here. Agents can use the protocol, but its there to handle the stuff the AI shouldn't need to see.
2.
by razvi0211 1y ago
> designing a truly universal description language for all possible service endpoint types and protocols is a hard (arguably impossible) problem Fair enough, but when restricting yourself to the problem of tool calling, giving the AI the
3.
by razvi0211 1y ago
Agreed! Right now, there's only one way to do tool calling, and that's MCP. I'm not happy with MCP, so I want alternatives so in the end we can all choose or create the best option. We're talking about the infrastructure
4.
by razvi0211 1y ago
Right now theres is only one option available for people creating agents, that lets the users of those agents add capabilities for the agents through tools. Its MCP. And to be honest, its not great, because its very opinionated, and requir
5.
by razvi0211 1y ago
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
6.
by razvi0211 1y ago
Funnily enough, thats exactly what UTCP is. Its just a way to let your AI leverage existing APIs instead of doing any wrapper protocols (like MCP) for the tool call. The protocol is only for discovery. It gets out of the way for the actual
7.
by razvi0211 1y ago
Hi thanks for sharing this! I'm the creator of the protocol. First of all this protocol is made as a completely open-source and community driven alternative to MCP. We're actively looking for contributors and general discussion to