ENTIA Entity Verification MCP

Get Entia Home

get_entia_home

Read-onlyIdempotent

FREE (no API key needed). Use when you already have an Entia Home URL path (country/sector/city/slug) and need that public business page as data. Retrieve the Schema.org JSON-LD @graph for a specific entity's Entia Home (machine layer at /v1/identity/{country}/{sector}/{city}/{slug}.jsonld). Requires country, sector, city, slug path segments — not cif/q. Obtain the path via entity_lookup / showcase (canonical_url). Fail-closed: never returns ENTIA corporate marketing as if it were the entity.

Input Schema

Name	Required	Description
`city`	Yes	City slug (madrid, barcelona, london)
`slug`	Yes	Business slug (clinica-dental-sonrisa)
`sector`	Yes	Industry slug (dental, legal, talleres, …)
`country`	Yes	ISO 3166-1 alpha-2 (es, gb, fr)

Output Schema

Name	Required	Description
`_meta`	No
`@graph`	No	WebPage, Entity, Verification Report and Territorial Profile nodes
`@context`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Full Schema.org @graph of an Entia Home page — the same truth as its public HTML twin.",
+  "properties": {
+    "@context": {
+      "type": "string"
+    },
+    "@graph": {
+      "description": "WebPage, Entity, Verification Report and Territorial Profile nodes",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "_meta": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedJul 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
AddedMay 26, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent/openWorld annotations, it discloses cost ('FREE, no API key needed') and a meaningful fail-closed semantic ('never returns ENTIA corporate marketing as if it were the entity'), which is the kind of non-obvious behavior risk an agent must know about. Return shape is covered by the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the most decision-relevant fact (free, no API key) and then the usage condition. Dense but every sentence carries information; it is slightly packed with endpoint/path detail that borders on redundant with the schema property descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-required-param read tool with full annotation coverage, complete schema descriptions, and an output schema, the description supplies the remaining pieces: cost/auth, path acquisition, fail-closed behavior, and the disallowed alternative input. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so individual parameter documentation is already handled. The description still adds value by giving the segment order and endpoint template and by stating what is NOT accepted (cif/q) and where valid values come from (canonical_url). Marginal gain above baseline, hence 4 rather than 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: retrieve the Schema.org JSON-LD @graph for a specific entity's Entia Home page. It even names the machine endpoint (/v1/identity/{country}/{sector}/{city}/{slug}.jsonld), which disambiguates it from entity_lookup, showcase, and the projection/dossier siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger condition ('when you already have an Entia Home URL path and need that public business page as data'), explicit prerequisite ('obtain the path via entity_lookup / showcase (canonical_url)'), and an explicit exclusion ('not cif/q'). An agent knows exactly when to pick this tool over alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ENTIA Entity Verification MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?