DatoQA

get_indicators

Read-onlyIdempotent

Annual population, GDP in current US dollars and CPI inflation from World Bank WDI worldwide economies. Use list_countries for supported three-character codes. Five completed years only, not real-time. Returns units, definitions, producers, footnotes and provenance. Null is missing, never zero. Not independently verified.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`country`	Yes	World Bank three-character economy code from list_countries, for example USA or FRA.
`language`	No	Response metadata language: en or fr; original producer attribution is preserved.	en
`indicator`	No	Optional annual series: population, gdp (current USD), or inflation (annual CPI percent). Omit for all three.

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	Yes
`items`	Yes
`notice`	No
`status`	Yes	Read this before using values; a successful transport does not establish data availability.
`country`	Yes
`coverage`	Yes
`language`	Yes
`returned`	Yes	Domain-specific result count, not necessarily the number of stored records in items.
`directory`	No
`interpretation`	Yes
`independently_verified`	No	Official-source checks are not independent factual corroboration.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / properties / items / items / properties / provenance / properties / verification_level / enum

Previous value: -[
-  "official_source_and_schema_checked",
-  "method_specific"
-]New value: +[
+  "official_source_and_schema_checked",
+  "public_aggregator_and_schema_checked",
+  "method_specific"
+]

First observedSep 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the read-only/idempotent annotations, it discloses freshness (five completed years only, not real-time), a critical data-semantics rule (null means missing, never zero), and a trust caveat (not independently verified). That is genuinely useful context for interpreting results, though it does not discuss rate limits or failure modes.

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?

Five short sentences, data scope front-loaded, no filler. The telegraphic style makes it dense but occasionally fragmentary (e.g. 'Not independently verified'), which slightly costs readability without wasting space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 structure need not be spelled out, yet the description still flags that units, definitions, producers, footnotes and provenance are returned, plus the null-handling rule. For a 3-parameter read tool this covers everything an agent needs.

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 coverage is 100%, so the schema already documents country, language, and indicator fully, including enum values and the default. The description adds only a mild restatement of the country code source and currency basis for gdp; the language parameter receives no elaboration, so baseline 3 is right.

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 the exact resource (World Bank WDI annual population, GDP in current USD, CPI inflation) and scope (worldwide economies), which lets an agent separate it from the many sibling indicator tools. It lacks an explicit verb, but the retrieval intent is unambiguous.

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?

It gives one real routing hint — use list_countries to obtain valid three-character codes — but offers no guidance on when to pick this over get_economic_indicators, get_historical_indicators, or get_us_economic_indicators, which compete for the same need.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DatoQA 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?