83/ 100

heatingplus.ro B

This site registers real WebMCP tools at runtime. Overall readiness is good, with room to improve.

Scanned 6 days ago with Chrome 151, 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 llms.txt present 4/4 pts

Found llms.txt (3,037 bytes).

PASS Not blocked by noindex 4/4 pts

No noindex directive found.

WebMCP tools, measured in a real browser43 / 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

7 tool(s) registered through modelContext.registerTool() while the page ran in our Chrome.

PART Tool schema quality 17/20 pts

Average schema quality 5.1/5 across 7 tool(s). Weakest: search_products (5/6), get_product_details (5/6), compare_products (5/6), estimate_heating_need (5/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 Origin Trial token 12/12 pts

Valid WebMCP token for heatingplus.ro, expires 17 Nov 2026.

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 sees6 / 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.

PASS Tools on more than the entry page 6/6 pts

All 10 checked pages expose tools.

FAIL The surface adapts to the page 0/14 pts

Every page exposes exactly the same tools, so nothing is tied to the current page.

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

Name	Description	Parameters	Read-only
`search_products`	Cauta produse publice in catalogul Heating Plus dupa denumire, marca, model sau cod. Folos...	2	no
`get_product_details`	Citeste datele publice structurate ale unei pagini de produs Heating Plus. Foloseste numai...	1	no
`browse_category`	Listeaza produse publice dintr-o categorie Heating Plus si returneaza denumirea categoriei...	2	no
`compare_products`	Compara intre doua si patru produse publice Heating Plus folosind datele structurate actua...	1	no
`estimate_heating_need`	Calculeaza orientativ necesarul termic pentru o centrala sau recomanda capacitatea BTU pen...	4	no
`search_guides`	Cauta in ghidurile publice Heating Plus articole despre alegere, montaj, consum, incalzire...	2	no
`get_site_policy`	Citeste informatiile publice oficiale Heating Plus despre livrare, retur, garantie, plata,...	1	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.

Talk to GOAI