Skip to main content
Glama

Statistics of the World

by com.statisticsoftheworld
OverviewDiscussionsAdmin

compare_sources

Compare source readings. Default mode returns latest IMF, World Bank and UN readings with their own years. For the 20-economy, 10-concept research pilot, provide country_id and year (exact year or common) to compare IMF and World Bank in the same period, inspect definition mismatches and retrieve recorded-state provenance. Optional as_of and revision pin SOTW stored state, not publisher availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoOpt into the research pilot: exact year or latest common past year. Requires country_id.
as_ofNoOptional SOTW recording cutoff: date at UTC midnight or ISO timestamp with timezone. Publisher availability is not established.
revisionNoArchive transaction watermark returned by an earlier comparison. Requires as_of.
country_idNoOptional ISO3 code to return a single country instead of all
indicator_idYesConcept key, e.g. IMF.NGDPD (GDP), IMF.NGDPDPC (GDP per capita), IMF.NGDP_RPCH (real growth)
processing_versionNoPin the comparison processing contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / as_of
      Added value: +{
+  "description": "Optional SOTW recording cutoff: date at UTC midnight or ISO timestamp with timezone. Publisher availability is not established.",
+  "type": "string"
+}
    • addedInput schema / properties / processing_version
      Added value: +{
+  "description": "Pin the comparison processing contract.",
+  "enum": [
+    "source-comparison-v1"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / revision
      Added value: +{
+  "description": "Archive transaction watermark returned by an earlier comparison. Requires as_of.",
+  "type": "string"
+}
    • addedInput schema / properties / year
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 2100,
+      "minimum": 1960,
+      "type": "integer"
+    },
+    {
+      "enum": [
+        "common"
+      ],
+      "type": "string"
+    }
+  ],
+  "description": "Opt into the research pilot: exact year or latest common past year. Requires country_id."
+}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains that as_of and revision pin SOTW stored state rather than publisher availability, and that the pilot mode exposes definition mismatches and provenance. It omits permissions, rate limits, and response shape, but the state-pinning caveat is a genuinely useful disclosure.

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?

Three front-loaded sentences with no filler: default behavior first, then the pilot-mode condition, then the optional pinning caveats. Some terms ('SOTW', 'recorded-state provenance') are jargon-heavy but each sentence earns its place.

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 comparison tool with no annotations and no output schema, the description covers both operating modes, the required coupling of parameters, and the meaning of as_of/revision pinning. Missing are auth needs and what a comparison result contains, but the core behavioral picture is complete enough to call correctly.

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%, so the schema already documents every parameter, including year, as_of, revision, and country_id. The description reinforces the coupling (year requires country_id, revision requires as_of) but adds little syntax or format information beyond what the schema states, warranting the baseline 3.

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 verb and resource ('Compare source readings') and enumerates what is returned by default (latest IMF, World Bank, UN readings with their own years), which is concrete. It distinguishes the two modes clearly, though it doesn't name the sibling compare_countries to route the agent away from it.

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 condition for switching modes: use the default, or supply country_id and year ('exact year or common') for the 20-economy, 10-concept pilot. It stops short of naming alternatives or stating when not to use the tool, so it is clear context without 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 Statistics of the World 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