Skip to main content
Glama

Monobank: exchange rates

mono_rates
Read-only

Fetch Monobank's UAH exchange rates for USD, EUR, PLN, and GBP by default, or request specific ISO currency codes to get buy, sell, or cross rates.

Instructions

Monobank exchange rates against the hryvnia: the price the bank buys and sells a currency at, or a cross rate for the less common ones. USD, EUR, PLN and GBP by default.

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

Input Schema

NameRequiredDescriptionDefault
currenciesNoISO codes such as ["USD", "CHF"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely new behavioral context by explaining that returns may be a bank buy/sell price or a cross rate for less common currencies, which tells the agent what the values mean. It omits freshness/update cadence and any auth or rate-limit notes.

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?

Two sentences, no filler, with the core resource stated first and the default-currency behavior appended where it is most useful. Nothing is redundant with the title or schema.

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 a single optional parameter and no output schema, the description carries the right amount of weight: it explains what the returned rates represent and what happens with no input. Only the data's freshness and source (bank rate timing) are left unstated, a minor gap for a read-only lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the currencies array and its ISO-code format are already documented, giving a baseline of 3. The description earns an extra point by disclosing the default behavior (USD, EUR, PLN, GBP when currencies is omitted), which the schema does not express.

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 states a specific resource (Monobank exchange rates against the hryvnia) and clarifies the two rate forms returned: buy/sell price and cross rate. It does not name or differentiate against any sibling, but the siblings (np_find_branch, np_quote, np_track) are unrelated, so disambiguation is not a real gap.

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 rather than stated: an agent can infer it should call this to obtain currency rates, and the mention of default currencies signals that calling with no arguments is valid. There is no explicit when-not guidance or statement of alternatives for fetching rates from another source.

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

Deploy Server

Other Tools