Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_orders

Retrieve and filter order records from POHODA accounting software by type, date range, company, order number, or ID. Returns matching orders as JSON data.

Instructions

List orders from POHODA. Supports filtering by order type, ID, date range, company name, order number, or last changes. Returns JSON array of matching order records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderTypeNoFilter by order type (issuedOrder or receivedOrder)
idNoFilter by order ID
dateFromNoFilter from date (DD.MM.YYYY or YYYY-MM-DD)
dateTillNoFilter till date (DD.MM.YYYY or YYYY-MM-DD)
companyNameNoFilter by company name
numberOrderNoFilter by order number
lastChangesNoFilter by last changes date

Implementation Reference

  • Implementation of the 'pohoda_list_orders' tool, which builds an XML request using POHODA's lst:listOrderRequest schema, sends it via the PohodaClient, and parses the response.
    server.tool(
      "pohoda_list_orders",
      "List orders from POHODA. Supports filtering by order type, ID, date range, company name, order number, or last changes. Returns JSON array of matching order records.",
      {
        orderType: orderTypeEnum.optional().describe("Filter by order type (issuedOrder or receivedOrder)"),
        id: z.number().optional().describe("Filter by order ID"),
        dateFrom: z.string().optional().describe("Filter from date (DD.MM.YYYY or YYYY-MM-DD)"),
        dateTill: z.string().optional().describe("Filter till date (DD.MM.YYYY or YYYY-MM-DD)"),
        companyName: z.string().optional().describe("Filter by company name"),
        numberOrder: z.string().optional().describe("Filter by order number"),
        lastChanges: z.string().optional().describe("Filter by last changes date"),
      },
      async (params) => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            "lst:listOrderRequest",
            NS.lst,
            "lst:requestOrder",
            (req) => {
              if (params.orderType) req.att("orderType", params.orderType);
              applyOrderFilter(req, {
                id: params.id,
                dateFrom: params.dateFrom,
                dateTill: params.dateTill,
                companyName: params.companyName,
                numberOrder: params.numberOrder,
                lastChanges: params.lastChanges,
              });
            }
          );
          const response = await client.sendXml(xml);
          const parsed = parseResponse(response);
          const data = extractListData(parsed);
          return jsonResult("Orders", data, Array.isArray(data) ? data.length : 0);
        } catch (e) {
          return err((e as Error).message);
        }
      }
    );
Behavior3/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. It compensates partially by disclosing the return format ('Returns JSON array') which is necessary given the lack of output schema. However, it omits safety profile (read-only status), pagination behavior, or rate limiting details that would help an agent understand operational constraints.

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?

Two sentences efficiently structured: first establishes the core operation and domain, second details capabilities and return format. No redundant text or tautology; every word contributes to agent understanding of the tool's scope.

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

Completeness4/5

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

For a list tool with 7 optional parameters and no output schema, the description adequately covers the return type and available filters. It could be improved by noting that all filters are optional (enabling full list retrieval) or mentioning pagination/result limits, but it provides sufficient context for basic invocation decisions.

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 baseline is 3. The description enumerates the available filters ('order type, ID, date range, company name, order number, or last changes') but adds minimal semantic value beyond what the schema already documents. It does not clarify the date format expectations or the semantics of 'last changes' beyond the schema text.

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

Purpose5/5

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

The description clearly states the specific verb 'List' with resource 'orders' from system 'POHODA'. It effectively distinguishes from sibling tools like pohoda_create_order and pohoda_delete_order, and differentiates from other list operations (invoices, addresses, etc.) by specifying the domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions filtering capabilities ('Supports filtering by...') but provides no explicit guidance on when to use this tool versus alternatives like pohoda_list_invoices or pohoda_list_offers. It also fails to note that all parameters are optional, which would be valuable context for agent selection.

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