Skip to main content
Glama
akutishevsky

Monobank MCP Server

get_client_info

Retrieve client details including account balances and savings jars from Monobank. Use this tool to access financial information for account management and monitoring.

Instructions

Get information about a client and a list of their accounts and jars. The tool can be called not more than 1 time per 60 seconds, otherwise an error will be thrown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the get_client_info MCP tool, which fetches client information from the Monobank API.
    server.tool(
        "get_client_info",
        "Get information about a client and a list of their accounts and jars. The tool can be called not more than 1 time per 60 seconds, otherwise an error will be thrown.",
        {},
        async () => {
            try {
                const { baseUrl, monobankApiToken } = getConfig();
                const response = await fetchWithErrorHandling(
                    `${baseUrl}/personal/client-info`,
                    {
                        headers: {
                            "X-Token": monobankApiToken,
                        },
                    },
                );
                const clientInfo = await parseJsonResponse<ClientInfo>(response);
                return createSuccessResponse(clientInfo);
            } catch (error) {
                return formatErrorAsToolResponse(error, "get client info");
            }
Behavior3/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 discloses the critical rate limit ('not more than 1 time per 60 seconds') and failure mode ('error will be thrown'), but omits read-only status, auth requirements, or caching behavior that would be expected for a retrieval tool.

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: the first states purpose, the second states the rate limit constraint. Both sentences are essential and front-loaded with no redundant or wasteful text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless tool, the description adequately mentions the return structure (client, accounts, jars) and rate limits. However, it lacks clarity on which client is retrieved (implied authenticated context) and provides no output schema details despite the absence of a formal output schema.

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 (empty schema), establishing a baseline score of 4 per evaluation rules. No parameter description is necessary or present.

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 uses a specific verb ('Get') and clearly identifies the resources retrieved: 'a client', 'accounts', and 'jars'. This distinguishes it from siblings get_currency_rates (exchange rates) and get_statement (transaction history).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the rate limit constraint is documented, there is no guidance on when to use this tool versus get_statement or get_currency_rates. No prerequisites or alternative selection criteria are provided.

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