[kordlessagain]

This is a terrible idea masquerading as innovation. Cloudflare wants you to believe LLMs write TypeScript better than they make tool calls, but they're really just creating another dependency on their infrastructure.

1. Tool calls are intentionally simple; adding a code generation layer introduces needless complexity and failure points.

2. Cloudflare already acts as a man-in-the-middle for ~20% of the Internet with limited transparency about government data requests

3. This is clearly designed to drive adoption of their Worker platform and create lock-in for AI agent developers

Similar to their x402 payment scheme that reinvents HTTP 402 under their control, the community has already built alternatives (see the Aperture implementation from Lightning) that don't require surrendering more of your stack to Cloudflare.

Remember what's happening here: a company with unprecedented visibility into web traffic wants even more control over how AI agents interact with the internet. Even if you don't believe that AI will eventually self govern itself, this is a horrible idea to limit individual's ability to automate portions of their access to the web.

No thanks.

[dennisy]

Whilst I agree that Cloudflare have a vested interest here, there have been other proposers of this concept such as huggingface.

https://huggingface.co/blog/smolagents

[danielser]

Is this not just GraphQL for MCP/Tools?

In which case your likely wrong, people do want it, and AI will be very good at orchestrating simple patterns.

CF definitely has a vested interest.. The problem for them now that I see is that THEY DIDN"T ACTUALLY LAUNCH IT... but did describe what it is/does in complete detail.

Now there are gonna be dozens of non CF locked clones, just like the one OP linked.