masafej536

this is a failure mode of consumer co-op that never occured to me. I thought the idea was bullet proof.

>Estimated bill updates remain paused

Wait what if someones actually getting usage spiked

If you owe AWS 140B dollars its their problem ;)

Something like this together with MCP can replace APIs for 3rd party integrations. You just give it instructions to "post a message in slack" and provide it slack MCP tools and it figures out the rest on its own. No need to read up on slack API docs or worry about breaking changes.

Point taken but there isnt any western providers there yet. Power is cheaper in china.

This looks like the same suicide inducing type of crap by google that previously only android devs on playstore were subject to.

They often do fail, at the client level you can just feed the schema validation error message back into the LLM and it corrects itself most of the time. If not the LLM throws itself into a loop until its caller times it out and it sends an error message back to the user.

At the server level it's just a good old JSON API at this point, and the server would send the usual error message it would send out to anyone.

llm tool call -> mcp client validates the schema -> mcp client calls the tool -> mcp server validates the schema -> mcp server responds with the result -> mcp client passes the tool result into llm