Skip to main content
Glama

Macro indicators for any country from the World Bank: GDP

econ_indicator
Read-only

Macro indicators for any country from the World Bank (CC BY 4.0): GDP, GDP growth, GDP per capita, inflation (CPI), unemployment, population, current account, government debt and lending interest rate, with the year, value and unit of each. Country by ISO2 or ISO3 code or exact name; indicator by friendly name or a raw World Bank code. Values lag by one to two years; years with no published value are left out. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>",
      "indicator": "<indicator>"
    },
    "name": "econ_indicator"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoHow many years back, 1 to 60, default 10
countryYesISO2 or ISO3 code (DE or DEU), or the country name, e.g. Germany
indicatorYesgdp, gdp-growth, gdp-per-capita, inflation, unemployment, population, current-account, government-debt, interest-rate, or a World Bank code such as NY.GDP.MKTP.CD

Output Schema

NameRequiredDescriptionDefault
seriesNo
sourceNo
countryNo
checkedAtNo
indicatorNo
disclaimerNo
lastUpdatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing cost ($0.002 per successful call, failed calls not charged), the payment mechanism (x402, USDC on Base/Solana and 10+ networks), data licensing (CC BY 4.0), and two data-freshness behaviors (one-to-two-year lag, silent omission of unpublished years). These are exactly the operational facts an agent needs before committing a paid call.

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?

The definition is front-loaded with purpose and data scope, then layers input formats, freshness caveats, and pricing in a tight sequence of semicolon-separated clauses. It is dense but each clause carries a distinct fact; the indicator enumeration is somewhat long and partly duplicates the schema enum-free description, which is the only waste.

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 full schema coverage, the description need not explain return values, yet it still notes that each result carries year, value, and unit. Cost, payment, input formats, and data lag are all covered. The only material omission is any pointer to a sibling tool for related macro or economic queries.

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 all three parameters including example values. The description restates accepted country forms (ISO2, ISO3, exact name) and indicator forms (friendly name or raw World Bank code such as NY.GDP.MKTP.CD), corroborating but not extending the schema, and it never mentions the 'years' parameter. Baseline 3 is appropriate when the schema carries the semantics.

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 a specific resource (macro indicators for any country from the World Bank) and enumerates the exact indicators served (GDP, GDP growth, inflation/CPI, unemployment, population, current account, government debt, interest rate). An agent can tell immediately what data comes back. It does not explicitly position itself against the similarly-named 'macro' sibling, so it stops short of a 5.

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?

Usage is implied rather than stated: the enumeration of indicators and the note that 'values lag by one to two years; years with no published value are left out' tells the agent when this data is appropriate and what it will not contain. There is no explicit when-to-use/when-not-to-use statement and no named alternative (e.g. the 'macro' sibling) for broader or different queries, leaving routing guidance to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources