Skip to main content
Glama
akutishevsky

Monobank MCP Server

get_currency_rates

Retrieve current currency exchange rates from Monobank API to support financial calculations and international transactions.

Instructions

Get a basic list of currency rates from Monobank. The information can be refreshed once per 5 minutes, otherwise an error will be thrown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the get_currency_rates tool, including registration and the async handler function that fetches and processes the currency data.
    server.tool(
        "get_currency_rates",
        "Get a basic list of currency rates from Monobank. The information can be refreshed once per 5 minutes, otherwise an error will be thrown.",
        {},
        async () => {
            try {
                const { baseUrl } = getConfig();
                const response = await fetchWithErrorHandling(
                    `${baseUrl}/bank/currency`,
                );
                const result = await parseJsonResponse<CurrencyRate[]>(response);
                const currencyRates = CurrencyRatesResponseSchema.parse(result);
                return createSuccessResponse(currencyRates);
            } catch (error) {
                return formatErrorAsToolResponse(error, "get currency rates");
            }
        },
    );
Behavior4/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the rate limiting behavior (5-minute refresh window) and error condition, though it could further improve by describing the return data structure since no output schema exists.

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 total, front-loaded with purpose ('Get a basic list...') followed immediately by the critical operational constraint (refresh rate). Every sentence earns its place with zero redundancy.

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 parameter-less read operation, the description adequately covers the primary complexity (rate limiting). However, given the lack of output schema, it could briefly mention what data the 'basic list' contains (e.g., buy/sell rates, currency pairs).

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?

The tool has zero parameters with 100% schema coverage (empty object), warranting the baseline score of 4. The phrase 'basic list' implicitly confirms no filtering parameters are available, aligning with the empty input schema.

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 clearly states the specific action ('Get'), resource ('basic list of currency rates'), and source ('Monobank'), effectively distinguishing this from siblings get_client_info and get_statement which handle client data and transaction history respectively.

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?

While it doesn't explicitly compare against sibling tools, it provides critical usage constraint information: the 5-minute refresh rate limit and the consequence of violation (error thrown), which guides the agent on call frequency.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/akutishevsky/monobank-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server