3 ms·

I don’t really get it — designing a truly universal description language for all possible service endpoint types and protocols is a hard (arguably impossible) p

I don’t really get it — designing a truly universal description language for all possible service endpoint types and protocols is a hard (arguably impossible) problem. Writing a client capable of parsing and using that description isn’t much easier. Unsurprisingly, it appears there’s no real spec: https://www.utcp.io/about/RFC https://www.utcp.io/about/RFC

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 ability to call APIs in a simplified way, rather than inventing a new communication protocol like MCP, is, in a lot of cases, better.