Skip to main content
Glama

StatCite — Verified Economic Statistics

by io.github.asokore

Get an economic indicator (with citation)

get_indicator
Read-onlyIdempotent

Get official values for a common economic indicator. Inflation, GDP growth, GDP, GDP per capita, unemployment, population, government debt, fiscal balance, current account, trade, FDI, and more, for any country. Returns the observations plus a full citation (source, dataset, series id, canonical URL, license, retrieval date) ready to cite in a report. Use ISO3 codes or plain country names. Start here for most questions; use search_indicators if unsure of the indicator key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesISO3/ISO2 code or English name, e.g. 'USA', 'Barbados', 'euro area'.
end_yearNoLast year to include (optional).
indicatorYesRegistry key, e.g. 'inflation_cpi', 'gdp_growth', 'unemployment_rate', 'govt_debt_gdp'. See search_indicators.
transformNoOptional transform computed by StatCite.
start_yearNoFirst year to include (optional).
latest_onlyNoReturn only the most recent non-null observation.
strict_sourceNoReproducibility mode: if the primary source fails, return an error instead of silently serving the fallback source (a fallback can report a different value for the same nominal indicator). Default false; fallback responses always carry fallback_used=true and a disclosure note.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds valuable behavioral context: it returns a full citation, mentions fallback behavior, and explains strict_source reproducibility mode. This goes beyond what annotations provide, though it doesn't cover every possible edge case.

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 three sentences, front-loaded with the core purpose, then lists supported indicators, citation details, and usage guidance. Every sentence provides value with no wasted words or redundant schema repetition.

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 no output schema, the description appropriately discloses the return format (observations plus a full citation) and key behavioral aspects like fallback and strict_source. It covers the main usage context and parameter hints adequately, though a bit more detail on the response structure would make it complete.

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 clarifying meaning beyond the schema, such as 'Use ISO3 codes or plain country names' and 'Registry key' for the indicator, enriching the parameter semantics. However, it doesn't fully detail every parameter, relying on the schema for specifics.

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 the tool's purpose: 'Get official values for a common economic indicator' and lists many indicator types. It also differentiates from siblings by positioning it as 'Start here for most questions' and explicitly mentioning search_indicators for when the indicator key is uncertain.

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

Usage Guidelines5/5

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

Explicitly says 'Start here for most questions' and directs users to 'use search_indicators if unsure of the indicator key.' This provides clear when-to-use and when-not-to-use guidance with a named alternative.

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

All StatCite — Verified Economic Statistics toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Tools are organized into clear functional groups (retrieval, search, verification, conversion), and pairs like get_indicator/get_series and verify_stat/verify_claims have explicit usage distinctions. The only minor overlap is between fetch and get_series, but their descriptions clarify when to use each.

Naming Consistency4/5

Most tool names follow a verb_noun snake_case pattern (get_indicator, verify_stat, compare_sources), with a few single-word or noun-style exceptions (fetch, search, country_snapshot). The overall convention is predictable and consistent.

Tool Count5/5

12 tools is within the optimal range for a domain of this complexity, covering retrieval, search, comparison, verification, conversion, and source listing without unnecessary bloat.

Completeness5/5

The surface covers the full workflow: discover indicators (search_indicators), search data (search), fetch data (get_indicator, get_series, fetch, country_snapshot), compare sources (compare_sources), convert values (fx_convert, inflation_adjust), verify claims (verify_stat, verify_claims), and understand sources (list_sources). No critical gaps are apparent.

Resources