Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_vyroba

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

Instructions

Export production documents (výroba) from POHODA

Input Schema

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

Implementation Reference

  • The handler for `pohoda_list_vyroba` that builds the XML request, sends it via the client, and returns the result.
    async (params) => {
      try {
        const xml = buildExportRequest(
          { ico: client.ico },
          "lst:listVyrobaRequest",
          NS.lst,
          "lst:requestVyroba",
          (req) => applyFilter(req, params),
        );
        const resp = parseResponse(await client.sendXml(xml));
        const data = extractListData(resp);
        return jsonResult("Production documents", data, data.length);
      } catch (e) {
        return err((e as Error).message);
      }
    },
  • Registration and definition of `pohoda_list_vyroba` tool.
    server.tool(
      "pohoda_list_vyroba",
      "Export production documents (výroba) from POHODA",
      {
        id: z.number().optional().describe("Document 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"),
      },
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 provides minimal information. While 'export' implies a read operation, the description does not specify the output format, pagination behavior, what happens when no documents match, or whether the operation is idempotent.

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 description is extremely concise at nine words. It is front-loaded with the verb 'Export' and wastes no text. However, the brevity contributes to the lack of behavioral and usage context, preventing a perfect score.

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 lack of annotations, output schema, and the presence of four optional filtering parameters, the description is incomplete. It fails to explain the return value format, the relationship between the date filters (AND/OR logic), or date string format expectations (ISO 8601, etc.).

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 for all four parameters, documenting them as 'Document ID', 'Date from', 'Date to', and 'Only changed after this date'. The description adds no additional parameter semantics, but with high schema coverage, the baseline score of 3 is appropriate.

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 resource ('production documents/výroba') from the POHODA system. It distinguishes this tool from siblings operating on different document types (invoices, orders, etc.) by specifying 'production documents'. However, it does not explicitly differentiate from the sibling 'pohoda_create_vyroba' beyond the implicit 'export' versus 'create' semantics.

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 this tool versus alternatives, or how to combine the optional filtering parameters (id, date range, lastChanges). There is no mention of prerequisites, permissions, or whether this retrieves current or historical production data.

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