FX Reference Rates

by dev.workers.regnotes.fx-reference-rates

macro_country

Read-only

Country economic profile: latest value and year plus annual history (2005 onward) for 21 World Bank World Development Indicators: GDP (USD), real GDP growth, GDP per capita, GNI per capita PPP, CPI inflation, unemployment, population, exports/imports % GDP, current account % GDP, central government debt % GDP, tax revenue % GDP, real and lending interest rates, FDI inflows % GDP, total reserves, official exchange rate, remittances % GDP, Gini, life expectancy, internet users. Country by ISO3/ISO2 code or name. CC BY 4.0. Price: $0.02 USDC per request (fixed; one paid HTTP GET = one charge; x402 exact on Base or MPP on Tempo; 4xx errors 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>"
    },
    "name": "macro_country"
  }
}

Input Schema

Name	Required	Description	Default
`years`	No	history years to include, 0-25, default 10
`country`	Yes	ISO 3166 alpha-3 or alpha-2 code or country name, e.g. JPN, US, Brazil

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely non-obvious behavior: history starts in 2005, cost is $0.02 USDC per request with one paid GET = one charge, 4xx errors are free, and data is CC BY 4.0. It does not say how missing indicators are represented, which is a minor remaining gap.

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?

Purpose and indicator scope are front-loaded in the first sentence, with country-code, licensing, and pricing details packed into short trailing sentences. The indicator list is long but each item is load-bearing for tool selection; there is little filler.

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 usefully states the return shape (latest value and year plus annual history) and enumerates covered indicators. Remaining gaps (response format, handling of indicators with no data) are minor for a read-only two-parameter tool.

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% and already documents both `country` (ISO3/ISO2/name) and `years` (0-25, default 10), so the description mostly repeats it. It does add the useful constraint that history only exists from 2005 onward, which caps the practical meaning of `years`, but that is modest added value.

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 resource (a country economic profile) and enumerates the 21 World Bank indicators returned, so an agent knows exactly what data comes back. It does not explicitly say how it differs from the sibling macro_indicator (single-indicator series) or macro_rank, leaving the boundary to inference.

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 by the content: fetch this when you want a broad country macro snapshot rather than one indicator series. There is no explicit when-to-use/when-not statement and no reference to macro_indicator or macro_rank as alternatives.

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

All FX Reference Rates tools Inspect

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

Need Help?