WebMCP / agent readiness
Agent readiness
WebMCP lets an agent act on your site. But an agent that cannot understand your site will not know which action to take, or whether to trust you enough to take it. Agent readiness is both layers: being understood, then being operable.
Two layers, in order
It is tempting to treat agent readiness as "add WebMCP and you are done." That skips the harder half. An agent arriving on your site has to answer two questions before it does anything useful: what is this, and can I rely on it? and only then what can I do here? The first is an understanding problem; the second is an action problem. WebMCP addresses the second. It does nothing for the first, and the first is where most sites actually fall down.
The understanding layer
Before an action is worth exposing, the agent has to comprehend the business behind it. That rests on signals AIOFacts documents in detail elsewhere:
- A clear entity. One unambiguous identity an agent can resolve, not a name that blurs into a similarly named company. See entity and entity strength.
- Structured data. Machine-readable facts, so an agent parses your offerings, hours, and identity rather than guessing them from prose.
- Readable, consistent content. The same story across your site and the wider web, because contradictions register as uncertainty and uncertainty suppresses action.
- Corroboration. Third-party references that let a system trust what you say about yourself.
These are the seven pillars in another frame. A site strong here is legible to an agent whether or not it ever ships a single tool.
Where reading conventions fit
The understanding layer also includes conventions aimed at AI readers. llms.txt, a static file that hints at what your content means, sits here: it helps an agent read you. It is worth separating cleanly from WebMCP, which lets an agent act. One is comprehension, the other is capability. A site can have either, both, or neither, and confusing them leads to spending on the wrong layer.
The action layer
Once a site is understood, exposing actions becomes worthwhile. That is WebMCP's job: publishing the high-value things an agent can do, search, book, quote, submit, as callable tools rather than an interface the agent has to reverse-engineer. Reaching for the action layer before the understanding layer is solid is the common mistake: a perfectly registered tool on a site the agent cannot identify or trust is a door on a building with no address.
What this means in mid-2026
The two layers are at very different stages, which sets a clear priority. The understanding layer pays off today: AI systems already read, cite, and represent businesses, so clear entities, structured data, and consistent facts have present value. The action layer, WebMCP, is pre-standard with no mainstream consumer yet. So the honest order of work is understanding first, where the return is real now, and action second, as an early, cheap, reversible bet on where the agentic web is going. Do the durable half well, and you are ready for the new half whenever it arrives.
Sources and related
- The seven pillars and the AIO glossary: the understanding-layer signals in detail.
- WebMCP and WebMCP readiness: the action layer and its honest status.
- webmachinelearning/webmcp: the WebMCP specification.
Reviewed 23 July 2026. The two-layer model is an AIOFacts position; the underlying signals and the WebMCP status are documented and dated on their own pages.
Put it to work
Understand it here. See it on a site. Build it with Digilu.
AIOFacts defines agent readiness. AIOInsights checks a specific site. Digilu decides with you whether, and how, to act.