Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_prijemky

Export receiving documents from POHODA accounting software by document ID, date range, or last changes using the MCP server integration.

Instructions

Export receiving documents (příjemky) 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 handler function for the list warehouse tool (which includes "pohoda_list_prijemky").
    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);
      }
    });
  • Registration of the tool "pohoda_list_prijemky".
    buildWarehouseListTool(server, client, "pohoda_list_prijemky", "Export receiving documents (příjemky) from POHODA", "lst:listPrijemkaRequest", "lst:requestPrijemka");
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 clarify whether this is a read-only operation, what data structure is returned, or whether there are pagination limits. The term 'Export' implies data retrieval but doesn't specify if this is destructive 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.

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the verb and resource. While appropriately brief, it lacks a second sentence that could have clarified output format or key behavioral constraints without sacrificing clarity.

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 both annotations and output schema, the description should explain what the tool returns (structured data vs. file) and provide basic usage patterns for the four optional parameters. As an ERP integration tool with complex sibling operations, the current single-sentence description is insufficient for reliable agent operation.

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 with clear explanations for each parameter (id, dateFrom, dateTill, lastChanges). The description adds no additional semantic context about parameter interactions (e.g., whether dateFrom requires dateTill), meeting the baseline expectation when the schema is self-documenting.

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 ('receiving documents/příjemky') and specifies the POHODA system context. However, the use of 'Export' rather than 'List' (used in the function name) creates slight ambiguity about whether this generates a file or returns data, and it doesn't explicitly differentiate from other list operations beyond naming the document type.

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 (e.g., pohoda_list_stock for inventory), nor does it explain the filtering strategy given that all four parameters are optional. There is no mention of prerequisites or required context.

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