ENTIA Entity Verification MCP

Get Showcase

get_showcase

Read-onlyIdempotent

FREE (no API key needed). Use to show example records and what ENTIA data looks like before choosing another tool. Curated IBEX35 + EU entity examples. FREE — does not consume quota. Use to explore data depth.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_showcase"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Sample size (default 3, max 5)
`category`	No	Subset to sample (default: all)

Output Schema

Name	Required	Description	Default
`_meta`	No
`unlock`	No
`checkout`	No
`entities`	No
`upgrade_url`	No
`access_level`	No
`gated_fields`	No
`upgrade_hint`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 30, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "Subset to sample (default: all)",
+  "enum": [
+    "all",
+    "ibex",
+    "tech",
+    "banking",
+    "energy",
+    "retail",
+    "spain",
+    "eu"
+  ],
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Sample size (default 3, max 5)",
+  "maximum": 5,
+  "minimum": 1,
+  "type": "integer"
+}

Changed1 schema field changedAug 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Curated sample entities for evaluation. Fields are gated by tier.",
+  "properties": {
+    "_meta": {
+      "type": "object"
+    },
+    "access_level": {
+      "type": "string"
+    },
+    "checkout": {
+      "type": "object"
+    },
+    "entities": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "gated_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "unlock": {
+      "type": "object"
+    },
+    "upgrade_hint": {
+      "type": "string"
+    },
+    "upgrade_url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedMay 26, 2026

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

removedInput schema / properties / category

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": "all",
-  "description": "Filter: 'all' | 'ibex' | 'tech' | 'banking' | 'energy' | 'retail' | 'spain' | 'eu'"
-}

removedInput schema / properties / limit

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": 10,
-  "description": "Max entities to return (default 10, max 50)"
-}

addedInput schema / required
```
Added value: +[]
```

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

First observedMay 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds genuinely new operational context — no API key needed and no quota consumption — which is exactly the kind of cost/access detail annotations cannot express. It does not cover rate limits or sample freshness, keeping it below a 5.

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

Conciseness3/5

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

Short and front-loaded, but 'FREE' is asserted three times across four sentences ('FREE (no API key needed)', 'FREE — does not consume quota'), which is redundant filler. Removing the duplicate would lose nothing.

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?

An output schema exists so return values need not be explained, there are no required parameters, and the access/cost model is disclosed. A preview tool needs little more, though noting which call to follow up with would make it fully self-sufficient.

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%, with both parameters documented including bounds and enum values, so the schema carries the burden. The description mentions the IBEX35/EU curation but does not map it to the category enum or add syntax beyond the schema.

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?

States a specific action — showing example records to illustrate what ENTIA data looks like — and scopes it to curated IBEX35 + EU entities. It positions itself as a preview step rather than a data operation, but does not name a specific sibling tool it complements.

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?

'Use to show example records ... before choosing another tool' and 'Use to explore data depth' give a clear trigger context. No explicit when-not conditions or named alternatives are given, so it stops short of full routing guidance.

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?