Skip to main content
Glama

DatoQA

by dev.workers.bhazarstudio.datoqa
OverviewDiscussionsAdmin

get_historical_indicators

Read-onlyIdempotent

Annual historical series for one World Bank country and indicator from 1960 to the last completed year. Use list_historical_indicators for keys and list_countries for countries. Choose GDP per capita, current dollars or constant 2015 dollars explicitly; these are not interchangeable. Nulls are missing, not zero. Provenance and original definitions included; not independently verified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclusive last observation year, no later than the last completed calendar year. Available data may end earlier.
fromNoInclusive first observation year, at least 1960 and no later than to.
formatNoCSV content with null flags, original values, source notes and provenance, alongside JSON. No missing-date filling.json
countryYesWorld Bank three-character economy code from list_countries, for example USA or FRA.
languageNoResponse metadata language: en or fr; original definitions and source notes are preserved.en
indicatorYesAnnual series key from list_historical_indicators, for example gdp_per_capita; inspect units before comparing.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / format
      Added value: +{
+  "default": "json",
+  "description": "CSV content with null flags, original values, source notes and provenance, alongside JSON. No missing-date filling.",
+  "enum": [
+    "json",
+    "csv"
+  ],
+  "type": "string"
+}
  2. 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"
  3. 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"
+]
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds non-obvious semantics: 'Nulls are missing, not zero' and 'Provenance and original definitions included; not independently verified.' These are genuine data-quality caveats not derivable from annotations or schema.

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?

Five short sentences, each carrying distinct information: scope, key/country sources, unit-choice warning, null semantics, and provenance disclaimer. No filler and the scope statement is front-loaded.

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?

With an output schema present and annotations covering safety, the remaining burden is mostly the unit/null/provenance caveats, which are all covered. Minor gap: no mention of payload size or pagination expectations for a 65-year annual series, though with the output schema present this is largely redundant.

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 baseline is 3; the description adds real meaning beyond it by warning that GDP per capita in current vs constant 2015 dollars 'are not interchangeable' and that units should be inspected before comparing. It does not elaborate on from/to or format beyond what the schema already documents.

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?

Names a specific verb+resource ('Annual historical series for one World Bank country and indicator from 1960 to the last completed year'), with clear scope and time bounds. It routes to list_historical_indicators for keys, which helps separate it from the sibling catalog tools, though it does not explicitly distinguish itself from get_economic_indicators or get_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?

Gives prerequisite routing ('Use list_historical_indicators for keys and list_countries for countries') and a real selection rule between GDP variants ('current dollars or constant 2015 dollars explicitly; these are not interchangeable'). It stops short of stating when to prefer this tool over the other indicator tools in the sibling list.

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