FX Reference Rates

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

macro_rank

Read-only

Country ranking: sort all economies by one World Development Indicator for a year (default: each country's latest value), highest first or lowest first, optionally filtered by World Bank region or income group. Aggregates (World, regions) excluded unless requested. 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": {
      "indicator": "<indicator>"
    },
    "name": "macro_rank"
  }
}

Input Schema

Name	Required	Description
`year`	No	year; default latest available per country
`limit`	No	1-300, default 50
`order`	No	desc (default) or asc
`income`	No	income group substring, e.g. High income, Lower middle
`region`	No	World Bank region substring, e.g. Latin America, Sub-Saharan
`indicator`	Yes	indicator key from /macro/indicators
`aggregates`	No	true to include regional/income aggregates

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the pricing model ($0.02 fixed per paid GET), that 4xx errors are not charged, the payment rails (x402 on Base, MPP on Tempo), and the licensing term (CC BY 4.0). It also flags the aggregate-exclusion default, which affects what comes back. That is unusually rich disclosure for an annotated read tool.

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?

Two sentences, purpose front-loaded, with defaults and the aggregate-exclusion rule packed into the first. The pricing/licensing sentence is dense but each clause carries operational value; nothing is genuinely wasted, though the packing is heavy.

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?

Purpose, defaults, filtering scope, and cost are all covered for a 7-parameter tool. With no output schema, the description still omits any hint of the return shape (e.g., ranked list of country/value pairs) and how limit interacts with the result set, which is the remaining gap.

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 description coverage is 100%, so every parameter is already documented, and the description mostly restates that (year default, highest/lowest ordering, aggregate exclusion). It does not address limit, income, or region substring matching beyond what the schema says, so it adds little beyond the baseline.

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?

"Country ranking: sort all economies by one World Development Indicator for a year" gives a specific verb (rank/sort), a specific resource (economies), and the axis of ranking. It implicitly but clearly distinguishes itself from siblings like macro_country (single-country lookup) and macro_indicator (indicator metadata).

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?

It states the default behavior (latest value per country), the default ordering (highest first), and the exclusion rule (aggregates like World and regions are dropped unless requested), which are exactly the decision points an agent needs. It does not explicitly name an alternative sibling or say when not to use it, so it falls short of a 5.

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?