Skip to main content
Glama

DatoQA

by dev.workers.bhazarstudio.datoqa
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
countryYesWorld Bank three-character economy code from list_countries, for example USA or FRA.
languageNoResponse metadata language: en or fr; original producer attribution is preserved.en
indicatorNoOptional annual series: population, gdp (current USD), or inflation (annual CPI percent). Omit for all three.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofYes
itemsYes
noticeNo
statusYesRead this before using values; a successful transport does not establish data availability.
countryYes
coverageYes
languageYes
returnedYesDomain-specific result count, not necessarily the number of stored records in items.
directoryNo
interpretationYes
independently_verifiedNoOfficial-source checks are not independent factual corroboration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • 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"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses meaningful data-quality behavior: null means missing and is never zero, the series covers only five completed years and is not real-time, and the data is not independently verified. These are exactly the caveats an agent needs to interpret results correctly and are not obtainable from the annotations.

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?

It is short, front-loaded with the core payload, and each sentence carries distinct information — scope, code lookup, temporal limit, return contents, null semantics, and verification caveat — with no filler.

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?

For a three-parameter read tool with 100% schema coverage, annotations, and an output schema, the description supplies the remaining interpretive context (null handling, data vintage, provenance, verification status) without redundantly explaining return values.

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?

Schema coverage is 100%, so the enum values and country-pattern are already documented and the baseline is 3. The description still adds value by pointing to list_countries for the three-character code and pinning the indicator meaning (current USD GDP, annual CPI percent) plus the five-completed-years constraint that the schema doesn't express.

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 specific resource and source (annual population, GDP in current USD, CPI inflation from World Bank WDI) and scopes it to worldwide economies, so an agent knows exactly what it retrieves. It narrows the field against the many sibling indicator tools by citing the WDI source and the five-completed-years limit, though it never explicitly names an alternative to distinguish from get_historical_indicators or get_economic_indicators.

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 clear operating context: use list_countries to obtain supported three-character codes, omit indicator for all three series, and note that only five completed years are available and data is not real-time. It stops short of explicitly stating when to prefer this tool over the adjacent indicator siblings, so the routing decision is implied rather than stated.

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

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