Skip to main content
Glama

Cash-service.pl

Kursy walut NBP (tabela A)

kursy_walut
Read-onlyIdempotent

Aktualne średnie kursy walut NBP z tabeli A - wszystkie albo jedna waluta (kod ISO, np. EUR).

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": "kursy_walut"
  }
}

Input Schema

NameRequiredDescriptionDefault
walutaNoKod ISO waluty, np. EUR, USD, GBP; puste = wszystkie

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?

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one genuinely new fact — "Aktualne" — signalling a current snapshot rather than historical rates, but says nothing about rate limits, data freshness, or publication cadence for a live NBP feed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the data source and scope stated first and the parameter behaviour second; there is no filler to remove.

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?

For a one-optional-parameter read tool with full annotations and no output schema, the definition covers source, scope and default behaviour adequately. A brief note on what table A returns (currency code plus mid rate) would close the last 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 coverage is 100% and the single optional parameter already documents the ISO code with examples and the empty-means-all default. The description merely restates "kod ISO, np. EUR", adding no format rules (case sensitivity, three-letter enforcement) beyond the schema.

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 resource precisely (NBP table A average exchange rates) and the scope (all currencies or one), so an agent knows exactly what comes back. It lacks an explicit verb and any sibling differentiation, though no sibling in the catalog concerns currencies, so mis-selection risk is low.

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 only implied: "wszystkie albo jedna waluta" tells the agent it can request everything or a single rate, but there is no statement of when to prefer this tool, no prerequisites, and no exclusions. With unrelated siblings the omission is minor, but it is still inference rather than guidance.

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