ENTIA Entity Verification MCP

Get Platform Stats

get_platform_stats

Read-onlyIdempotent

FREE (no API key needed). Use when the user asks how much data ENTIA covers (entities, BORME acts). Live platform stats: total entities and BORME acts, counted live. Country and Entia Home counts are null (marked _unverified) until they are measured.

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_platform_stats"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output 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 changedNov 5, 2026
- changedOutput schema / properties / homes_published / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / jsonld_generated / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
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

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the baseline is low. The description still adds real value beyond them by disclosing that no API key is needed and that country and Entia Home counts may come back null and are marked _unverified, which prevents the agent from misreading missing values as zeros.

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?

The access note and the usage trigger are front-loaded, and three sentences cover access, trigger, and return content without padding. The phrase 'counted live' slightly duplicates 'Live platform stats', a minor redundancy.

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 shape need not be explained, and the description covers the remaining gaps: cost/auth, when to call it, and the meaning of null fields. Nothing essential is missing for a parameterless stats tool.

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 there is nothing for the description to disambiguate. The baseline of 4 applies and no gap exists here.

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 names a specific resource and the concrete values returned (total entities and BORME acts), so the agent knows exactly what it gets. It does not differentiate itself from siblings like get_entia_home or zone_profile, which is the only thing separating it from a 5.

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 an explicit trigger: 'Use when the user asks how much data ENTIA covers (entities, BORME acts).' That is a clear usage condition, but there are no when-not conditions or named alternatives for overlapping coverage questions.

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?