ENTIA Entity Verification

Zone Profile

zone_profile

Read-onlyIdempotent

PAID (requires SIGNAL plan or higher, from €29/month). Use when the user asks about the income, employment, demographics, business census or real-estate profile of a Spanish postal code. Socioeconomic profile of a Spanish postal code — 17 blocks: income, employment, demographics, business census, real estate, FTTH, poverty, tourism.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postal_code": "<postal_code>"
    },
    "name": "zone_profile"
  }
}

Input Schema

Name	Required	Description	Default
`postal_code`	Yes	Spanish 5-digit postal code (28013 = Madrid Gran Vía)

Output Schema

Name	Required	Description	Default
`_meta`	No
`economy`	No
`province`	No
`income_aeat`	No
`postal_code`	No
`real_estate`	No
`municipality`	No
`employment_sepe`	No
`businesses_dirce`	No
`demographics_ine`	No
`autonomous_community`	No
`entia_classification`	No
`digital_infrastructure`	No
`poverty_inequality_ccaa`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026
- changedInput schema / properties / postal_code / pattern
```
Previous value: -"^[0-9]{5}$"New value: +"^[0-9]{4,5}$"
```

Changed1 schema field changedAug 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Socioeconomic profile of a Spanish postal code, 17 blocks from official sources.",
+  "properties": {
+    "_meta": {
+      "type": "object"
+    },
+    "autonomous_community": {
+      "type": "string"
+    },
+    "businesses_dirce": {
+      "type": "object"
+    },
+    "demographics_ine": {
+      "type": "object"
+    },
+    "digital_infrastructure": {
+      "type": "object"
+    },
+    "economy": {
+      "type": "object"
+    },
+    "employment_sepe": {
+      "type": "object"
+    },
+    "entia_classification": {
+      "type": "object"
+    },
+    "income_aeat": {
+      "type": "object"
+    },
+    "municipality": {
+      "type": "string"
+    },
+    "postal_code": {
+      "type": "string"
+    },
+    "poverty_inequality_ccaa": {
+      "type": "object"
+    },
+    "province": {
+      "type": "string"
+    },
+    "real_estate": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedMay 26, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / postal_code / description

Previous value: -"Spanish 5-digit postal code (e.g. 28013 for Madrid Gran Vía). Spain only — UK/FR/etc. return empty."New value: +"Spanish 5-digit postal code (28013 = Madrid Gran Vía)"

changedInput schema / properties / postal_code / pattern
```
Previous value: -"^\\d{5}$"New value: +"^[0-9]{5}$"
```

AddedMay 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds valuable context beyond annotations: it is a paid tool requiring the SIGNAL plan or higher, from €29/month, which is important operational information an agent needs before invoking it.

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

Conciseness5/5

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

The description is two tightly constructed sentences. It front-loads the paid-plan requirement and usage trigger, then lists the data blocks efficiently with no wasted words.

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

Completeness4/5

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

With an output schema present, the description does not need to explain return values in detail. It covers the key prerequisites (paid plan), the use case, and the broad data coverage, though it could clarify sibling alternatives for an agent choosing among the many lookup tools.

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

Parameters3/5

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

Schema description coverage is 100% and the single postal_code parameter already has a clear description with an example (28013 = Madrid Gran Vía). The tool description adds no additional parameter syntax or constraints beyond what the schema provides, so the baseline of 3 applies.

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

Purpose4/5

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

The description clearly states the resource: a socioeconomic profile of a Spanish postal code, with 17 blocks including income, employment, demographics, business census, real estate, FTTH, poverty, and tourism. It is specific enough for an agent to know what the tool returns, though it does not explicitly differentiate itself from sibling tools such as entity_lookup or get_full_dossier.

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

Usage Guidelines4/5

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

It gives a clear usage trigger: 'Use when the user asks about the income, employment, demographics, business census or real-estate profile of a Spanish postal code.' It does not mention when not to use the tool or name alternative siblings, so it stops short of a 5.

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