Google just shipped an official "agent-ready" toolkit. Here's the one thing it can't measure.

For most of 2026, "is my website agent-ready?" was a question you answered with vibes and a blog post. As of last week, Chrome answers it with a toolkit.

On June 22, the Chrome team , the remediation advice still holds. I don't want to re-run it here. I want to talk about the one thing this toolkit — by design — cannot tell you.

What the toolkit measures

The WebMCP portion of the audit, per the blog, "checks for the availability of registered WebMCP tools, forms missing declarative WebMCP, and schema validity." In plain terms it asks three questions:

1. Did your page register any tools via navigator.modelContext (or declarative form annotations)?


2. Are there forms that should be exposed as tools but aren't?


3. Are the input/output schemas valid?

That's a genuinely useful static check. It tells you whether you've done the work of exposing your site's logic. Pass it and an agent that shows up has a clean, structured way to call your search, your cart, your booking form — instead of screenshotting the page and guessing where to click.

The thing it can't measure

Here's the gap. Every check in that toolkit is about exposure: have you offered the tools? None of them — and none of them can, because they run at audit time in your own browser — tell you whether a real agent, in production, ever called one.

Exposure and invocation are two different facts:

• 
  Exposure is a property of your code. Static. Auditable. Pass/fail. The toolkit nails it.


• 
  Invocation is a property of the world. It's "on Tuesday at 14:03, something calling itself Gemini-in-Chrome invoked searchProducts({query:'waterproof'}) and got 8 results back." No static audit can know that, because it hasn't happened yet when the audit runs.

For most of this year the honest knock on WebMCP was "no mainstream agent calls navigator.modelContext anyway." That's changing — Google has , a one-line script that does both halves: it exposes your existing search/cart/forms as WebMCP tools (so you pass the new audit), and its hosted tier records which agents call which tools and whether the calls succeed — the invocation layer a static audit can't see. The free, MIT client is on GitHub; you can wire up the same logging by hand with the snippet above if you'd rather.

Either way, the takeaway stands on its own: Chrome now grades you on whether you offer tools to agents. Whether agents actually take them is a separate fact — and right now, almost nobody is watching it. The day Gemini-in-Chrome makes its first call to your site is worth seeing happen. Make sure you can.