Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_prevodky

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

Instructions

Export transfer documents (převodky) 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 tool handler logic for listing documents in POHODA, used by pohoda_list_prevodky.
    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 pohoda_list_prevodky tool.
    buildWarehouseListTool(server, client, "pohoda_list_prevodky", "Export transfer documents (převodky) from POHODA", "lst:listPrevodkaRequest", "lst:requestPrevodka");
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Export' implies a read-only operation, the description does not confirm this, nor does it disclose side effects, rate limits, authentication requirements, pagination behavior, or the format of returned data.

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

Conciseness5/5

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

The description consists of a single, efficient sentence with no redundant words. Every element serves to identify the tool's function, making it appropriately front-loaded and concise.

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

Completeness3/5

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

Given the 100% input schema coverage, the input side is adequately documented. However, there is no output schema, no annotations, and the description does not explain what data structure is returned or how filtering logic works (e.g., whether filters are AND/OR combined). This leaves significant gaps for a data retrieval tool.

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?

With 100% schema description coverage, the input parameters (id, dateFrom, dateTill, lastChanges) are fully documented in the schema itself. The description does not add additional semantic context about parameter interactions or date formats beyond what the schema provides, warranting the baseline score of 3.

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 uses a specific verb 'Export' and resource 'transfer documents (převodky)', clearly indicating it retrieves transfer documents from the POHODA system. It implicitly distinguishes from sibling 'pohoda_create_prevodka' by using 'Export' (read) versus the implied write operation of 'create'.

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 such as 'pohoda_create_prevodka' or other list operations like 'pohoda_list_stock'. There are no explicit when-to-use conditions, prerequisites, or exclusions stated.

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