Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_movements

Retrieve and filter movement records from POHODA accounting software by date range. This read-only export returns JSON data for inventory tracking and analysis.

Instructions

List movement records from POHODA. Read-only export. Supports filtering by date range. Returns JSON array of movement records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateFromNoFilter from date (DD.MM.YYYY or YYYY-MM-DD)
dateTillNoFilter till date (DD.MM.YYYY or YYYY-MM-DD)

Implementation Reference

  • The implementation of the `pohoda_list_movements` tool, including its registration, parameter schema, and the handler function that builds the XML request, calls the POHODA client, and processes the response.
    server.tool(
      "pohoda_list_movements",
      "List movement records from POHODA. Read-only export. Supports filtering by date range. Returns JSON array of movement records.",
      {
        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)"),
      },
      async (params) => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            "lst:listMovementRequest",
            NS.lst,
            "lst:requestMovement",
            (req) => applyFilter(req, params)
          );
          const response = await client.sendXml(xml);
          const parsed = parseResponse(response);
          const data = extractListData(parsed);
          return jsonResult("Movements", 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?

Without annotations, the description carries the full disclosure burden. It successfully indicates the read-only nature and return format (JSON array), but omits pagination behavior, rate limits, maximum date ranges, or authorization requirements that would be necessary for robust agent operation.

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 efficiently structured in four short sentences with the action verb front-loaded. No words are wasted, though the content is minimalistic rather than richly informative.

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 absence of annotations and output schema, the description adequately covers the basic contract by mentioning the JSON array return type. However, it lacks detail on what constitutes a 'movement record' (fields, structure) or default behaviors when filtering isn't provided.

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 coverage, the baseline is 3. The description confirms date range filtering is supported, but adds no additional semantic value regarding parameter interactions, date format preferences, or default behavior when parameters are omitted (both are optional per schema).

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 states the tool lists 'movement records' from POHODA, using a specific verb and resource. It distinguishes from siblings like pohoda_list_stock and pohoda_list_invoices by specifying 'movements', though it could clarify whether these are stock movements or financial transactions for perfect clarity.

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 notes 'Read-only export' implying safe data retrieval usage, but provides no explicit guidance on when to select this tool over similar siblings (e.g., pohoda_list_stock vs pohoda_list_movements) or prerequisites like date range requirements.

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