Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_vydejky

Export dispatch documents from POHODA accounting software by specifying document ID, date range, or last changes filter.

Instructions

Export dispatch documents (výdejky) from POHODA

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoDocument ID
dateFromNoDate from (DD.MM.YYYY or YYYY-MM-DD)
dateTillNoDate to
lastChangesNoOnly changed after this date

Implementation Reference

  • Registration of the pohoda_list_vydejky tool using the buildWarehouseListTool helper.
    buildWarehouseListTool(server, client, "pohoda_list_vydejky", "Export dispatch documents (výdejky) from POHODA", "lst:listVydejkaRequest", "lst:requestVydejka");
  • The handler logic for pohoda_list_vydejky (and other list tools) which constructs an XML request, sends it to the Pohoda client, parses the response, and returns the result.
    function buildWarehouseListTool(
      server: McpServer,
      client: PohodaClient,
      toolName: string,
      description: string,
      listTag: string,
      requestTag: string,
    ) {
      server.tool(toolName, description, listFilterFields, async (params) => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            listTag,
            NS.lst,
            requestTag,
            (req) => applyFilter(req, params),
          );
          const resp = parseResponse(await client.sendXml(xml));
          const data = extractListData(resp);
          return jsonResult(description, data, data.length);
        } catch (e) {
          return err((e as Error).message);
        }
      });
    }
  • Input schema definition for the list tools, including pohoda_list_vydejky.
    const listFilterFields = {
      id: z.number().optional().describe("Document ID"),
      dateFrom: z.string().optional().describe("Date from (DD.MM.YYYY or YYYY-MM-DD)"),
      dateTill: z.string().optional().describe("Date to"),
      lastChanges: z.string().optional().describe("Only changed after this date"),
    };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to deliver. It does not clarify whether this is a read-only operation, what data structure is returned (critical given the lack of output schema), pagination behavior, or error handling conditions.

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

Conciseness4/5

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

The single sentence is efficient with no wasted words, front-loading the key action and resource. Every element serves a purpose, though given the complexity (four parameters, no output schema, no annotations), the description is arguably undersized rather than optimally concise.

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?

Given the absence of output schema and annotations, the description is insufficient for an agent to fully understand the tool's behavior. It lacks explanation of return values, filtering logic (AND/OR), and whether the operation is safe to invoke, leaving significant gaps for a tool interfacing with an accounting system.

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?

The input schema has 100% description coverage, documenting all four parameters (id, dateFrom, dateTill, lastChanges) including date formats. Since the schema is self-documenting, the baseline score applies, though the description adds no additional semantic context about parameter relationships or optional usage.

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

Purpose4/5

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

The description clearly identifies the action ('Export') and the specific resource ('dispatch documents' with the Czech term 'výdejky') from the POHODA system. However, it does not explicitly differentiate this tool from similar listing tools like pohoda_list_prijemky or pohoda_list_prodejky, nor does it clarify the exact nature of the 'export' operation.

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?

The description provides no guidance on when to use this tool versus alternatives, or how to effectively use the optional filtering parameters. It fails to mention that all four parameters are optional or explain the interaction between date range and ID filtering.

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