Skip to main content
Glama

Get an economic indicator (with citation)

get_indicator
Read-onlyIdempotent

Retrieve official values for economic indicators like inflation, GDP, and unemployment for any country, complete with a full citation for reports.

Instructions

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.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that it returns observations plus a full citation, and the strict_source parameter describes fallback behavior. Does not contradict annotations. Adds moderate value beyond structured fields.

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?

Two sentences with no redundancy. Every sentence adds distinct value (purpose, usage hint, examples). Front-loaded with core purpose.

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?

Given 7 parameters and no output schema, the description covers return values (observations + citation) and fallback behavior. Could be slightly more detailed on response structure, but overall sufficient for agent usage.

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% but description adds examples for indicator (e.g., 'inflation_cpi', 'gdp_growth') and country ('ISO3 codes or plain country names'), and explains strict_source fallback. Provides practical guidance beyond schema definitions.

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?

Description uses specific verbs ('Get official values') and lists numerous examples of indicators, clearly distinguishing from siblings like search_indicators which is for finding indicator keys. The resource (economic indicator with citation) is well-defined.

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?

Explicitly says 'Start here for most questions' and directs to search_indicators when unsure of the indicator key. Provides clear context but could further exclude other siblings like country_snapshot for cross-country comparisons.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asokore/statcite'

If you have feedback or need assistance with the MCP directory API, please join our Discord server