“It might cost you half a million tokens to do it and be really error prone, because the website didn't just expose the tools in a reasonable way. All WebMCP is, is: here's a command that I can run, here's a title and description for it so the agent can understand what it is, and here's a schema for how to call it. That's it. It's just a function call. But because it's in plain language, like a skill, the LLM can slurp that up.”

right. And can you see that like you're, I don't know, there's, there's the sidebar on the left and the browser on the left, and you're kind of seeing it do the work. That's what WebMCP kind of unlocks and it can do so really efficiently. That's neat. And

…like, here's my known traveler number or what my TSA, you know, just go chuck that in there. What, you know, like, like, get me as far as you can in the process and then I'll finish it. You know, like, I think I would, I would appreciate that just because I hate doing that, you know. And then it

Yeah. I mean, I'm, yeah, I don't, I think it does need to go slower. I think if you just hit full send on it, you know, you'd be bad. It

is, right? Because you call this function to register the command. What if people start writing that function right in the middle of their JavaScript? It's going to throw in another browser. And now it's something's broken in Firefox because Chrome shipped it or whatever. They're not. Nobody's…

you could build your API kind of, you know, like. You know, and then you just, and those are just internal functions, and then your MCP just calls internal functions, hopefully. You know, it's like not calling new, net new code, you know, it's like,