Skip to main content
Glama

finwire.pl - Polish financial data

NBP exchange rates and gold

get_currency_rates
Read-onlyIdempotent

Use for exchange rates and the gold price. NBP mid, bid and ask rates of currencies against PLN (table), the history of one currency, or the NBP gold price (code "XAU").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_currency_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoISO code, e.g. EUR, USD, CHF; "XAU" for gold. Omit for the main currencies.
daysNoHistory window in days for one currency, default 90.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description adds useful domain context (rates are NBP mid/bid/ask quoted against PLN, "XAU" selects gold, days applies to a single currency) but says nothing about caching, freshness, or limits, and the output schema already covers return shape.

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 short sentences, front-loaded with the usage trigger, then the mode enumeration. The parenthetical "(table)" and the dense "NBP mid, bid and ask" phrasing are slightly compressed jargon but every clause carries information.

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, full parameter descriptions and rich read-only annotations, the description only needs to explain modes and the gold special case, which it does. Minor gaps remain on how the default no-code table behaves and whether the currency list is fixed.

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 both parameters are already documented, including the omit-for-main-currencies default and the 90-day default. The description's only added meaning is the "XAU" mapping and the implication that days is meaningful only in single-currency history mode — consistent with the baseline 3 when the schema does the heavy lifting.

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 the specific resource (NBP mid/bid/ask rates against PLN) and enumerates its three modes: full table, single-currency history, and gold price via code "XAU". That is far more than a restatement of the name, though it never explicitly contrasts itself with siblings such as get_bank_rates or get_interest_rates.

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?

"Use for exchange rates and the gold price" gives a clear trigger, and the mode list tells the agent which call shape to pick. It stops short of stating exclusions or naming an alternative tool for related rate data.

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.