Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_offers

Retrieve and filter business offers from POHODA accounting software by type, ID, date range, company name, or last changes.

Instructions

List offers from POHODA. Supports filtering by offer type (issued/received), ID, date range, company name, or last changes. Returns JSON array of matching offer records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offerTypeNoFilter by offer type (issuedOffer or receivedOffer)
idNoFilter by offer 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
lastChangesNoFilter by last changes date

Implementation Reference

  • The tool 'pohoda_list_offers' is registered here with its schema definition within the registerOfferTools function.
    server.tool(
      "pohoda_list_offers",
      "List offers from POHODA. Supports filtering by offer type (issued/received), ID, date range, company name, or last changes. Returns JSON array of matching offer records.",
      {
        offerType: offerTypeEnum.optional().describe("Filter by offer type (issuedOffer or receivedOffer)"),
        id: z.number().optional().describe("Filter by offer 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"),
        lastChanges: z.string().optional().describe("Filter by last changes date"),
      },
  • The handler implementation for 'pohoda_list_offers' which builds the XML request, sends it to the Pohoda client, and parses the response.
    async (params) => {
      try {
        const xml = buildExportRequest(
          { ico: client.ico },
          "lst:listOfferRequest",
          NS.lst,
          "lst:requestOffer",
          (req) => {
            if (params.offerType) req.att("offerType", params.offerType);
            const filterParams: ListFilterParams = {
              id: params.id,
              dateFrom: params.dateFrom,
              dateTill: params.dateTill,
              companyName: params.companyName,
              lastChanges: params.lastChanges,
            };
            applyFilter(req, filterParams);
          }
        );
        const response = await client.sendXml(xml);
        const parsed = parseResponse(response);
        const data = extractListData(parsed);
        return jsonResult("Offers", 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?

With no annotations provided, the description discloses return format ('JSON array of matching offer records') but omits safety characteristics, pagination behavior, rate limits, or error conditions. It implies read-only behavior but does not confirm it.

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?

Three sentences with zero waste: purpose front-loaded in sentence one, capabilities in sentence two, and return format in sentence three. No redundant phrases or unnecessary verbosity.

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?

Adequately compensates for missing output schema by specifying the JSON array return type. With 100% schema parameter coverage, it appropriately focuses on high-level functionality rather than parameter repetition, though it could note that all filters are optional.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given 100% schema coverage, the description adds semantic value by framing parameters as 'filtering' criteria and mapping enum values ('issued/received' vs schema's 'issuedOffer/receivedOffer'), clarifying their interactive purpose beyond raw schema definitions.

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 uses specific verb 'List' with clear resource 'offers from POHODA', distinguishing it from sibling creation tools like pohoda_create_offer and other list operations such as pohoda_list_orders or pohoda_list_invoices.

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?

While the description implies retrieval usage through 'List' and 'filtering', it lacks explicit guidance on when to prefer this over pohoda_create_offer or whether offers must exist first. No alternatives or exclusions are 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