Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_accountancy

Export accountancy records from POHODA software with date-based filtering. Retrieve financial data as JSON for reporting and analysis.

Instructions

List accountancy records from POHODA. Read-only export. Supports filtering by date range or last changes. Returns JSON array of accountancy 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)
lastChangesNoFilter by last changes date

Implementation Reference

  • The handler function for the `pohoda_list_accountancy` tool. It builds the XML request, sends it via the client, parses the response, and returns the result as JSON.
    async (params) => {
      try {
        const xml = buildExportRequest(
          { ico: client.ico },
          "lst:listAccountancyRequest",
          NS.lst,
          "lst:requestAccountancy",
          (req) => applyFilter(req, params)
        );
        const response = await client.sendXml(xml);
        const parsed = parseResponse(response);
        const data = extractListData(parsed);
        return jsonResult("Accountancy", data, Array.isArray(data) ? data.length : 0);
      } catch (e) {
        return err((e as Error).message);
      }
    }
  • Registration of the `pohoda_list_accountancy` tool, including its name, description, and input schema using zod.
    server.tool(
      "pohoda_list_accountancy",
      "List accountancy records from POHODA. Read-only export. Supports filtering by date range or last changes. Returns JSON array of accountancy 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)"),
        lastChanges: z.string().optional().describe("Filter by last changes date"),
      },
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses 'Read-only export' (safety) and 'Returns JSON array' (return format), but lacks pagination details, volume limits, or field structure of the returned records.

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, zero waste. Front-loaded with action verb, followed by safety profile, capabilities, and return type. Every sentence earns its place with no 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 simple 3-parameter list tool without output schema, the description covers purpose, safety, filters, and return type adequately. Minor gap: does not mention pagination behavior or whether parameters are optional (though schema shows this).

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 has 100% description coverage with date formats already specified. Description mentions filtering capabilities align with parameters but adds no additional semantic value (e.g., whether dateFrom/dateTill are inclusive, or lastChanges format details). Baseline 3 appropriate given schema completeness.

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?

Description uses specific verb 'List' with clear resource 'accountancy records from POHODA'. The term 'accountancy' effectively distinguishes this tool from 20+ sibling list tools (e.g., list_invoices, list_orders) by specifying the exact record 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?

Mentions 'Supports filtering by date range or last changes' which implies usage patterns, but lacks explicit when-to-use guidance or differentiation from related list tools. No mention of what happens when no filters are provided (full export vs error).

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