ENTIA Entity Verification MCP

Get Platform Stats

get_platform_stats

Read-onlyIdempotent

Live platform stats: total entities and BORME acts, counted live. Country and Entia Home counts are null (marked _unverified) until they are measured.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	No
`status`	No
`cache_ttl`	No
`countries`	No
`borme_acts`	No
`_unverified`	No	Figures NOT independently verified — honesty marker, do not quote as verified
`last_updated`	No
`sources_active`	No
`total_entities`	No
`homes_published`	No
`countries_active`	No
`jsonld_generated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026
- changedOutput schema / properties / countries / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
- changedOutput schema / properties / countries_active / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```

Changed1 schema field changedAug 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Live platform totals. Single source of truth for corpus size.",
+  "properties": {
+    "_meta": {
+      "type": "object"
+    },
+    "_unverified": {
+      "description": "Figures NOT independently verified — honesty marker, do not quote as verified",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "borme_acts": {
+      "type": "integer"
+    },
+    "cache_ttl": {
+      "type": "integer"
+    },
+    "countries": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "countries_active": {
+      "type": "integer"
+    },
+    "homes_published": {
+      "type": "integer"
+    },
+    "jsonld_generated": {
+      "type": "integer"
+    },
+    "last_updated": {
+      "type": "string"
+    },
+    "sources_active": {
+      "type": "integer"
+    },
+    "status": {
+      "type": "string"
+    },
+    "total_entities": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedMay 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description adds real behavioral context: counts are computed live rather than cached, and Country/Entia Home values may be null and flagged _unverified until measured. That caveat prevents an agent from misreading placeholder nulls as real zero values.

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?

Two tight sentences with no filler. The core scope (total entities and BORME acts) is front-loaded, and the data-quality caveat follows only because it changes how the result should be read.

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 no explanation, and with no parameters there is little else to document. The description supplies the one thing the structured data cannot convey — that nulls are unmeasured rather than genuinely empty — though it stops short of routing the agent relative to sibling tools.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description's mention of _unverified relates to output fields, which is covered by the output schema rather than parameter semantics.

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 resource and its contents: platform-wide totals for entities and BORME acts. It is clearly an aggregate-stats tool, distinct in kind from the entity-specific lookups among its siblings, though it never names or contrasts with them explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated — an agent infers this is a global overview call as opposed to per-entity tools like entity_lookup or get_entity_home. No when-to-use or when-not-to-use guidance and no named alternatives are given.

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?