Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_prodejky

Export sales documents from POHODA accounting software by specifying document ID, date range, or recent changes for integration with MCP-compatible clients.

Instructions

Export sales documents (prodejky) 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

  • The buildWarehouseListTool function serves as a factory handler that defines the logic for listing warehouse documents, including 'pohoda_list_prodejky'. It 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);
        }
      });
    }
  • The 'pohoda_list_prodejky' tool is registered in the registerWarehouseTools function using the buildWarehouseListTool factory.
    buildWarehouseListTool(server, client, "pohoda_list_prodejky", "Export sales documents (prodejky) from POHODA", "lst:listProdejkaRequest", "lst:requestProdejka");
    buildWarehouseCreateTool(server, client, "pohoda_create_prodejka", "Create a sales document (prodejka) in POHODA", NS.pro, "pro", "prodejka", "prodejkaHeader", "prodejkaDetail", "prodejkaItem");
  • The input validation schema (listFilterFields) for 'pohoda_list_prodejky' and other warehouse list tools.
    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?

No annotations provided, so description carries full burden, yet discloses nothing about read-only safety, return format, pagination, or whether 'Export' implies file generation or data retrieval. Fails to mention all parameters are optional.

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?

Extremely concise at 6 words with no filler. However, the brevity comes at the cost of missing critical context given zero annotations and no output schema.

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?

With 4 filter parameters, no output schema, and no annotations, the description is inadequate. It fails to describe the return structure, pagination behavior, or filtering logic (AND/OR between parameters).

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%, so parameters are fully documented in the schema. The description adds no parameter-specific guidance (e.g., date formats, ID uniqueness), earning the baseline score for high-coverage schemas.

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?

States specific verb 'Export' and resource 'sales documents (prodejky) from POHODA', distinguishing from sibling create/delete operations. However, uses 'Export' while tool name uses 'list', and doesn't explicitly differentiate from other list_* siblings (e.g., pohoda_list_invoices).

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?

Provides no guidance on when to use this tool versus alternatives like pohoda_list_invoices or pohoda_create_prodejka. No explanation of when to filter by id vs date ranges vs lastChanges.

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