Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_enquiries

Retrieve and filter enquiry records from POHODA accounting software by type, date range, company, or ID to manage business inquiries.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enquiryTypeNoFilter by enquiry type (issuedEnquiry or receivedEnquiry)
idNoFilter by enquiry 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 implementation of the 'pohoda_list_enquiries' tool, including its schema definition and handler logic for fetching enquiries from the POHODA client.
    server.tool(
      "pohoda_list_enquiries",
      "List enquiries from POHODA. Supports filtering by enquiry type (issued/received), ID, date range, company name, or last changes. Returns JSON array of matching enquiry records.",
      {
        enquiryType: enquiryTypeEnum.optional().describe("Filter by enquiry type (issuedEnquiry or receivedEnquiry)"),
        id: z.number().optional().describe("Filter by enquiry 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"),
      },
      async (params) => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            "lst:listEnquiryRequest",
            NS.lst,
            "lst:requestEnquiry",
            (req) => {
              if (params.enquiryType) req.att("enquiryType", params.enquiryType);
              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("Enquiries", 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 carries the full disclosure burden. It adds crucial information about the return format ('JSON array'), but omits important behavioral details like pagination behavior, record limits, or explicit confirmation that this is a read-only operation.

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 efficiently structured sentences with zero waste. The first sentence front-loads the core purpose, while the second covers capabilities and return type without redundancy.

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?

Given the absence of an output schema, the description appropriately discloses the return type ('JSON array of matching enquiry records'). With 100% parameter coverage and 6 optional parameters, it adequately covers the filtering interface, though it could mention pagination or default limits.

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 enumerates the available filters but adds no semantic value beyond what the schema already provides (e.g., no examples, format guidance beyond the schema, or cross-parameter relationships).

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') and resource ('enquiries from POHODA'), distinguishing it from sibling tools like 'pohoda_create_enquiry' (create vs list) and other list operations targeting different document types (invoices, orders, etc.).

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 implies usage by detailing available filters (enquiry type, date range, company name), but provides no explicit guidance on when to use this tool versus alternatives like 'pohoda_create_enquiry' or when to prefer specific filters over others.

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