Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_balance

Retrieve balance records from POHODA accounting software. Filter by date range to export financial data as JSON for analysis and reporting.

Instructions

List balance records from POHODA. Read-only export. Supports filtering by date range. Returns JSON array of balance records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateFromNoFilter from date (DD.MM.YYYY or YYYY-MM-DD)
dateTillNoFilter till date (DD.MM.YYYY or YYYY-MM-DD)

Implementation Reference

  • Implementation of the `pohoda_list_balance` MCP tool handler in `src/tools/reports.ts`.
    server.tool(
      "pohoda_list_balance",
      "List balance records from POHODA. Read-only export. Supports filtering by date range. Returns JSON array of balance records.",
      {
        dateFrom: z.string().optional().describe("Filter from date (DD.MM.YYYY or YYYY-MM-DD)"),
        dateTill: z.string().optional().describe("Filter till date (DD.MM.YYYY or YYYY-MM-DD)"),
      },
      async (params) => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            "lst:listBalanceRequest",
            NS.lst,
            "lst:requestBalance",
            (req) => applyFilter(req, params)
          );
          const response = await client.sendXml(xml);
          const parsed = parseResponse(response);
          const data = extractListData(parsed);
          return jsonResult("Balance", data, Array.isArray(data) ? data.length : 0);
        } catch (e) {
          return err((e as Error).message);
        }
      }
    );
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses read-only nature and return format ('JSON array'). Missing pagination details or error behavior, but covers basic safety and output expectations for a simple export 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?

Four sentences, each earning its place: purpose declaration, safety hint, parameter scope, and return format. Front-loaded with the core action and no redundant text.

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?

Appropriate for a 2-parameter list tool. Compensates for missing output schema by stating return type. Could improve by clarifying what constitutes a 'balance record' in POHODA (accounting vs inventory context).

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% with detailed date format descriptions. Description mentions 'Supports filtering by date range' which semantically connects to the two parameters. Baseline 3 appropriate since schema does the heavy lifting.

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?

Clear specific verb ('List') + resource ('balance records from POHODA'). Distinguishes from write-oriented siblings (create/delete/update variants) by identifying the specific entity type being queried.

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?

Implies usage through 'Read-only export' which signals safe querying vs mutation tools, but lacks explicit guidance on when to use this versus sibling list operations like pohoda_list_accountancy or pohoda_list_bank.

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/hlebtkachenko/pohoda-mcp'

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