Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_service

Export service records from POHODA accounting software by specifying ID, date range, or last changes.

Instructions

Export service records from POHODA

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoService record ID
dateFromNoDate from
dateTillNoDate to
lastChangesNoOnly changed after this date

Implementation Reference

  • The "pohoda_list_service" tool is defined and implemented in src/tools/production.ts. It uses buildExportRequest to construct the request, sends it via the PohodaClient, and returns the parsed list data.
    server.tool(
      "pohoda_list_service",
      "Export service records from POHODA",
      {
        id: z.number().optional().describe("Service record ID"),
        dateFrom: z.string().optional().describe("Date from"),
        dateTill: z.string().optional().describe("Date to"),
        lastChanges: z.string().optional().describe("Only changed after this date"),
      },
      async (params) => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            "lst:listServiceRequest",
            NS.lst,
            "lst:requestService",
            (req) => applyFilter(req, params),
          );
          const resp = parseResponse(await client.sendXml(xml));
          const data = extractListData(resp);
          return jsonResult("Service records", data, data.length);
        } catch (e) {
          return err((e as Error).message);
        }
      },
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but discloses almost nothing about safety, idempotency, pagination, return format, or whether 'Export' implies file generation. It does not clarify if the operation is read-only or has side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (5 words), which avoids verbosity, but it is under-structured—presenting as a fragment rather than front-loaded sentences. Every word earns its place, but there is insufficient content to guide usage.

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

Completeness2/5

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

For a tool with 4 filter parameters and no output schema, the description is incomplete. It fails to explain parameter interaction logic (AND vs OR), expected return structure, or filtering behavior when no parameters are provided (all records?).

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 description coverage is 100% (all 4 parameters have basic descriptions), so the description meets the baseline. However, it adds no semantic context about date formats, ID uniqueness, or the relationship between dateFrom/dateTill and lastChanges parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description provides a verb ('Export') and resource ('service records from POHODA'), but 'Export' is ambiguous compared to the tool name 'list_service'—it is unclear whether this retrieves data or generates a file export. It distinguishes the resource (services vs siblings like invoices/orders) but does not clarify the operation's nature.

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?

No guidance provided on when to use ID filtering versus date ranges, or how to combine the optional parameters. No mention of sibling alternatives like pohoda_create_service or when to use pohoda_download_file instead.

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