SiteCheck Crypto & Finance

World Bank indicator values for one country by year, e.g

finance_world_bank

Read-only

World Bank indicator values for one country by year, e.g. GDP in current US dollars (NY.GDP.MKTP.CD), from the World Bank open data API. Annual data; the latest years can be missing or revised. Related tools on this server, for a different need: finance_bcb_brazil_central_bank when you need Brazil Central Bank SGS time series: the latest N values; finance_asian_dev_bank_data when you need Asian Development Bank financing from ADB's official IATI. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); 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": "finance_world_bank"
  }
}

Input Schema

Name	Required	Description
`years`	No	How many most recent years, 1 to 30 (default 5)
`country`	Yes	ISO 2 or 3 letter country code, e.g. US, DEU, BR
`indicator`	Yes	World Bank indicator code, e.g. NY.GDP.MKTP.CD, SP.POP.TOTL

Output Schema

Name	Required	Description	Default
`rows`	No
`source`	No
`country`	No
`checkedAt`	No
`indicator`	No
`lastUpdated`	No
`indicatorCode`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations it discloses data-quality behavior (annual frequency, latest years may be missing or revised) and the commercial/payment behavior: $0.002 USDC per successful call via x402 on Base, Solana or Arc, with failed calls not charged. Cost and failure-charging semantics are exactly the kind of thing an agent cannot infer from annotations.

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 caveats come first and the routing/pricing tail is informative rather than filler. The final sentence is long and slightly run-on, packing payment chain options and pricing into one clause, but nothing is redundant.

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, return format need not be explained, and the description covers sourcing, caveats, alternatives and cost. The only soft spot is the phrase 'by year', which could be read as selecting a specific year while the years parameter is actually a count of most recent years.

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 both required parameters (country ISO code, indicator code) are already documented with examples, so the baseline is 3. The description adds only marginal meaning, though 'annual data; latest years can be missing or revised' usefully frames what the years count actually returns.

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 opens with a specific verb+resource+scope: indicator values for one country across recent years, sourced from the World Bank open data API, and gives concrete indicator codes (NY.GDP.MKTP.CD). It is clearly distinguishable from the crypto-heavy sibling list and from the other finance data providers.

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?

It explicitly routes to alternatives with conditions: use finance_bcb_brazil_central_bank for Brazil Central Bank SGS series returning the latest N values, and finance_asian_dev_bank_data for ADB IATI financing data. That is an explicit when-to-use-which rule rather than implied usage.

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

All SiteCheck Crypto & Finance 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?