Skip to main content
Glama

ENTIA Entity Verification

by io.github.entia-systems-core
OverviewDiscussionsAdmin

Get Platform Stats

get_platform_stats
Read-onlyIdempotent

Live platform stats: entities count, countries, sources, homes published.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_metaNo
statusNo
cache_ttlNo
countriesNo
borme_actsNo
_unverifiedNoFigures NOT independently verified — honesty marker, do not quote as verified
last_updatedNo
sources_activeNo
total_entitiesNo
homes_publishedNo
countries_activeNo
jsonld_generatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / required
      Added value: +[]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety and idempotency. The description adds 'Live' to indicate real-time data, which is useful but not critical. No additional behavioral traits (e.g., rate limits, caching) are disclosed.

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 a single, front-loaded sentence that efficiently communicates the tool's purpose and output. Every word adds value, and there is no repetition or irrelevant detail.

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?

For a zero-parameter tool with rich annotations and an output schema, the description is largely complete. It specifies the nature ('Live') and the data categories. However, it could briefly mention that the output is a structured object matching the schema, or clarify whether 'Live' implies real-time vs. cached.

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?

No parameters exist, so schema coverage is 100%. The description does not need to explain parameters. The baseline of 4 is appropriate since the tool requires no input and the description lists the output fields.

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

Purpose5/5

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

The description clearly states it provides 'Live platform stats' and lists specific metrics: entities count, countries, sources, homes published. The verb 'get' combined with resource 'platform stats' is unambiguous and distinct from siblings like entity_lookup or get_showcase.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. The sibling list includes other stats-like tools (e.g., get_entia_home, get_showcase), but the description offers no context for differentiation, such as scope or use case.

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