Runs your page in a real browser. No guessing. Blog Leaderboard Contact RO EN
85/ 100

aerconditionatservice.ro A

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

Scanned 1 hour 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 browser38 / 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
1 tool(s) registered through modelContext.registerTool() while the page ran in our Chrome.
PART Tool schema quality 9/14 pts
Average schema quality 4/5 across 1 tool(s). Weakest: listeaza_servicii_aer_conditionat (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 1 names follow the verb and object form. To rename: listeaza_servicii_aer_conditionat.
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.
PASS Origin Trial token 12/12 pts
Valid WebMCP token for aerconditionatservice.ro, expires 30 Mar 2027.
Discovery, community conventions12 / 12
Not part of the official Chrome spec. Scored as a small bonus because static crawlers and directories use it.
PASS Discovery manifest at /.well-known/webmcp 6/6 pts
Valid JSON manifest found.
PASS Manifest describes tools 3/3 pts
7 tool(s) described in the manifest.
PASS Manifest served as application/json 3/3 pts
Content-Type is application/json.
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
listeaza_servicii_aer_conditionat Listează serviciile de aer condiționat, tarifele publicate relevante și programul de lucru... 0 yes

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.

Talk to GOAI