Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_invoices

Retrieve and filter invoice records from POHODA accounting software by type, date range, company details, or other criteria. Returns matching invoices as JSON data.

Instructions

List invoices from POHODA. Supports filtering by invoice type, ID, date range, variable symbol, company name, IČO, or last changes. Returns JSON array of matching invoice records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invoiceTypeNoFilter by invoice type
idNoFilter by invoice ID
dateFromNoFilter from date (DD.MM.YYYY or YYYY-MM-DD)
dateTillNoFilter till date (DD.MM.YYYY or YYYY-MM-DD)
variableSymbolNoFilter by variable symbol
companyNameNoFilter by company name
icoNoFilter by IČO
lastChangesNoFilter by last changes date

Implementation Reference

  • The handler function for 'pohoda_list_invoices' that builds the XML export request, sends it via the client, and returns the parsed list of invoices.
      async (params) => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            "lst:listInvoiceRequest",
            NS.lst,
            "lst:requestInvoice",
            (req) => {
              if (params.invoiceType) req.att("invoiceType", params.invoiceType);
              const filterParams: InvoiceFilterParams = {
                id: params.id,
                dateFrom: params.dateFrom,
                dateTill: params.dateTill,
                variableSymbol: params.variableSymbol,
                companyName: params.companyName,
                ico: params.ico,
                lastChanges: params.lastChanges,
              };
              applyInvoiceFilter(req, filterParams);
            }
          );
          const response = await client.sendXml(xml);
          const parsed = parseResponse(response);
          const data = extractListData(parsed);
          return jsonResult("Invoices", data, Array.isArray(data) ? data.length : 0);
        } catch (e) {
          return err((e as Error).message);
        }
      }
    );
  • Registration of 'pohoda_list_invoices' tool with its input schema definitions using Zod.
    server.tool(
      "pohoda_list_invoices",
      "List invoices from POHODA. Supports filtering by invoice type, ID, date range, variable symbol, company name, IČO, or last changes. Returns JSON array of matching invoice records.",
      {
        invoiceType: invoiceTypeEnum.optional().describe("Filter by invoice type"),
        id: z.number().optional().describe("Filter by invoice 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)"),
        variableSymbol: z.string().optional().describe("Filter by variable symbol"),
        companyName: z.string().optional().describe("Filter by company name"),
        ico: z.string().optional().describe("Filter by IČO"),
        lastChanges: z.string().optional().describe("Filter by last changes date"),
      },
Behavior3/5

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

With no annotations provided, the description must carry full behavioral burden. It successfully discloses the return format ('Returns JSON array'), but omits critical operational details like read-only safety status, pagination behavior, rate limits, or error handling patterns.

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 two efficient sentences with zero waste. It is appropriately front-loaded with the core action ('List invoices') followed by filter capabilities and return format, earning its brevity.

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 8 parameters, no output schema, and no annotations, the description partially compensates by specifying the JSON array return type. However, it lacks detail on the structure/content of invoice records and omits safety/permission context that annotations would typically provide.

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, establishing a baseline of 3. The description adds value by summarizing the filter categories (invoice type, ID, date range, etc.), but does not extend beyond the schema's existing documentation to provide format examples or dependency relationships between parameters.

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 verb (List) and resource (invoices from POHODA), making the core purpose unambiguous. However, it does not explicitly differentiate from sibling list tools (e.g., pohoda_list_accountancy or pohoda_list_orders) or contrast with pohoda_create_invoice/delete_invoice.

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?

While the description enumerates available filters, it provides no guidance on when to use this tool versus alternatives like pohoda_list_accountancy, nor does it clarify prerequisites or indicate that all parameters are optional (0 required params).

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