What it is, how to implement it, how to verify it. Services AI agent readiness audit WebMCP Implementation Agentic SEO architecture Structured data and schemas API optimization and data layer for AI Knowledge graph and entity modeling WebMCP migration and refactoring WebMCP consulting for companies and agencies WebMCP for online stores Origin trial and technical compliance WebMCP maintenance and monitoring See all services Blog Leaderboard RO EN
62/ 100

aerconditionatservice.ro C

This site registers real WebMCP tools at runtime. Overall readiness is moderate.

Scanned 3 days ago with Chrome 158, real execution with a modelContext interceptor and synthetic interaction.

Scan another site

Agent access22 / 22
PASS Page loads over HTTPS 8/8 pts
The page answered with HTTP 200 over HTTPS.
PASS AI agents allowed in robots.txt 6/6 pts
No major AI crawler is blocked in robots.txt.
PASS AI crawlers named explicitly in robots.txt recommendation, no points
8 AI crawlers are named explicitly in robots.txt.
PASS llms.txt present 4/4 pts
Found llms.txt (6,138 bytes).
PASS Not blocked by noindex 4/4 pts
No noindex directive found.
WebMCP tools, measured in a real browser27 / 46
We load the page in Chrome, intercept modelContext before any script runs and record what your page actually registers.
PASS WebMCP tools detected at runtime 14/14 pts
3 tool(s) registered through modelContext.registerTool() while the page ran in our Chrome.
PART Tool schema quality 10/14 pts
Average schema quality 4.3/6 across 3 tool(s). Weakest: lista_servicii_aer_conditionat (4/6), programeaza_interventie_ac (5/6), aboneaza_aer_reminder (4/6).
How to fix: Give every tool a clear description, a JSON Schema with typed and described parameters, constraints (enum, minLength, pattern, format), additionalProperties: false, and readOnlyHint annotations where they apply.
PASS Declarative form field quality 3/3 pts
No declarative forms; imperative tool parameters are evaluated under schema quality.
FAIL Tool names made of a verb and an object 0/3 pts
0 of 3 names follow the verb and object form. To rename: lista_servicii_aer_conditionat, programeaza_interventie_ac, aboneaza_aer_reminder.
How to fix: Name each tool after the action it performs: a verb followed by its object, for example search_products, get_order_status or submit_contact_form. A vague name (data, form1, search) forces the agent to read the description to guess what the tool does.
FAIL Origin Trial token 0/12 pts
No origin-trial token found. While WebMCP is in origin trial, stable Chrome only exposes modelContext to origins that serve a valid token.
How to fix: Register your origin at developer.chrome.com/origintrials for the WebMCP trial and serve the token in a meta http-equiv="origin-trial" tag. Without it, stable Chrome does not expose modelContext to your visitors while the API is in trial.
Discovery, community conventions0 / 12
Not part of the official Chrome spec. Scored as a small bonus because static crawlers and directories use it.
FAIL Discovery manifest at /.well-known/webmcp 0/6 pts
No valid JSON at /.well-known/webmcp (status 404).
How to fix: Publish a JSON file at /.well-known/webmcp describing your tools. It is not part of the official spec, but it lets crawlers and static tools discover what your site offers.
FAIL Manifest describes tools 0/3 pts
The manifest does not describe any tools.
How to fix: Add a "tools" array with name, description and inputSchema for each tool.
FAIL Manifest served as application/json 0/3 pts
No manifest to evaluate.
How to fix: Serve the manifest with the Content-Type: application/json header.
Coverage, how much of the site the agent sees13 / 20
We open several inner pages and check whether the tools travel with the user through the site or sit only on the entry page.
PART Tools on more than the entry page 2/6 pts
Only 3 of 10 checked pages expose tools.
How to fix: Register tools across the site, not only on the landing page. An agent that arrives straight on an inner page, from a search or a link, has to find what it needs there.
PART The surface adapts to the page 11/14 pts
3 distinct tool sets across 3 pages. The surface adapts across several sections of the site; there is room for one more context.
How to fix: Add tools tied to the page the agent is on: the details of that product or service, that page form, search within the current section. The same tools everywhere is a header, not a capability.

Tools registered by this page

NameDescriptionParametersRead-only
lista_servicii_aer_conditionat Listează serviciile de aer condiționat, tarifele publicate relevante și programul de lucru... 0 yes
programeaza_interventie_ac Trimite o cerere de programare către echipă. Este doar o solicitare; programarea devine co... 13 no
aboneaza_aer_reminder Înregistrează clientul în AERreminder folosind formularul și lista CSV existente. Sunt obl... 4 no

Captured live from modelContext.registerTool() calls while the page ran. A static HTML scan cannot see these.

Not measurable remotely, so not scored: end-to-end tool execution by an agent, human-in-the-loop consent handling, and result quality. Test those with the Model Context Tool Inspector extension in a WebMCP-capable Chrome.

Push this score higher?

GOAI implements WebMCP end to end: imperative tools, valid schemas, the origin trial token and the discovery manifest.

See our services