Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_internal_docs

List and filter internal documents from POHODA accounting software by ID, date range, or last changes. Returns matching records as JSON array.

Instructions

List internal documents from POHODA. Supports filtering by ID, date range, or last changes. Returns JSON array of matching records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoFilter by internal document ID
dateFromNoFilter from date (DD.MM.YYYY or YYYY-MM-DD)
dateTillNoFilter till date (DD.MM.YYYY or YYYY-MM-DD)
lastChangesNoFilter by last changes date

Implementation Reference

  • The handler function for the 'pohoda_list_internal_docs' tool. It builds an XML request, sends it to the Pohoda client, parses the response, and extracts the list data.
    async (params) => {
      try {
        const xml = buildExportRequest(
          { ico: client.ico },
          "lst:listIntDocRequest",
          NS.lst,
          "lst:requestIntDoc",
          (req) => applyFilter(req, params)
        );
        const response = await client.sendXml(xml);
        const parsed = parseResponse(response);
        const data = extractListData(parsed);
        return jsonResult("Internal documents", data, Array.isArray(data) ? data.length : 0);
      } catch (e) {
        return err((e as Error).message);
      }
    }
  • The registration of the 'pohoda_list_internal_docs' tool using the McpServer instance.
    server.tool(
      "pohoda_list_internal_docs",
      "List internal documents from POHODA. Supports filtering by ID, date range, or last changes. Returns JSON array of matching records.",
      {
        id: z.number().optional().describe("Filter by internal document 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)"),
        lastChanges: z.string().optional().describe("Filter by last changes date"),
      },
      async (params) => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            "lst:listIntDocRequest",
            NS.lst,
            "lst:requestIntDoc",
            (req) => applyFilter(req, params)
          );
          const response = await client.sendXml(xml);
          const parsed = parseResponse(response);
          const data = extractListData(parsed);
          return jsonResult("Internal documents", 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 provided, so description carries full burden. It discloses the return format ('JSON array of matching records'), which compensates somewhat for the missing output schema. However, it lacks critical safety context (read-only assurance, idempotency), pagination behavior, or rate limiting details expected for a data retrieval tool without annotation coverage.

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 well-structured sentences with zero waste: first establishes purpose, second covers capabilities and return format. Every sentence earns its place; appropriately front-loaded.

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?

Adequate for a simple 4-parameter retrieval tool with complete schema documentation. Mentioning the JSON array return partially compensates for missing output schema. However, lacks completeness regarding result limits, pagination, or what constitutes a 'matching record' structure.

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?

Schema description coverage is 100%, establishing baseline 3. The description summarizes available filters ('ID, date range, or last changes') but adds no syntax details, format examples, or semantic relationships beyond what the schema already provides (e.g., does not clarify date format precedence between DD.MM.YYYY and YYYY-MM-DD).

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?

States specific verb (List) and resource (internal documents from POHODA), matching the tool name. However, it does not differentiate from sibling list tools (e.g., pohoda_list_invoices, pohoda_list_contracts) by explaining what constitutes an 'internal document' in this context.

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?

Lists filtering capabilities but provides no guidance on when to use this tool versus alternatives. Does not mention relationship to pohoda_create_internal_doc or other document-listing siblings, nor prerequisites like authentication or date format preferences.

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