ENTIA Entity Verification

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.

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

Changed2 schema fields changedMay 26, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / required
```
Added value: +[]
```
First observedMay 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint. The description adds useful behavioral context beyond annotations: it is free/no API key, stats are counted live, and country/Entia Home counts are null and marked _unverified until measured. These are meaningful caveats about data quality and freshness.

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 description is short and front-loads the most important fact ('FREE (no API key needed)'). There is minor redundancy in 'Live platform stats' and 'counted live,' but otherwise every sentence adds useful information.

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 the description need not explain return values. It covers the key caveat about null _unverified fields and the live-counting behavior, making it complete enough for an agent to call correctly. It could be slightly richer about what counts are included, but nothing essential 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?

There are zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and the input schema is empty and fully described.

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 states a specific resource (live platform stats: total entities and BORME acts) and frames it around coverage questions. It is clear what the tool returns, though it does not explicitly differentiate itself from sibling tools beyond the coverage angle.

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 how much data ENTIA covers (entities, BORME acts).' It does not name when not to use it or point to alternatives, but the context is unambiguous.

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.