Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

by hlebtkachenko
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

pohoda_list_vouchers

Retrieve cash vouchers (receipts and expenses) from POHODA accounting software. Filter results by ID, date range, company name, or last changes to access specific financial records.

Instructions

List cash vouchers (receipts and expenses) from POHODA. Supports filtering by ID, date range, company name, or last changes. Returns JSON array of matching records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoFilter by voucher 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

  • src/tools/vouchers.ts:31-47 (handler)
    The handler function for 'pohoda_list_vouchers' which builds the XML request, sends it via the client, and parses/returns the voucher list.
    async (params) => {
  try {
    const xml = buildExportRequest(
      { ico: client.ico },
      "lst:listCashRequest",
      NS.lst,
      "lst:requestCash",
      (req) => applyFilter(req, params)
    );
    const response = await client.sendXml(xml);
    const parsed = parseResponse(response);
    const data = extractListData(parsed);
    return jsonResult("Vouchers", data, Array.isArray(data) ? data.length : 0);
  } catch (e) {
    return err((e as Error).message);
  }
}
  • src/tools/vouchers.ts:22-30 (registration)
    The registration and input schema definition for 'pohoda_list_vouchers'.
    "pohoda_list_vouchers",
"List cash vouchers (receipts and expenses) from POHODA. Supports filtering by ID, date range, company name, or last changes. Returns JSON array of matching records.",
{
  id: z.number().optional().describe("Filter by voucher 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"),
},

Tool Definition Quality

B3.4/5.0
Behavior3/5

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

Discloses return format ('Returns JSON array of matching records'), which is necessary given the lack of output schema. However, with no annotations provided, the description fails to indicate the safety profile (read-only vs destructive), pagination behavior, or rate limits that the agent needs to know.

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?

Three sentences with clear structure: purpose first, filters second, return format third. No redundant or wasted language. Appropriately terse for a simple listing tool.

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 5-parameter list operation with 100% schema coverage. The description compensates for missing output schema by stating the return type. However, given zero annotations, it should explicitly state the read-only/safe nature of the operation to be complete.

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 the filtering capabilities ('Supports filtering by...') but adds no semantic detail beyond the schema (e.g., date format precedence, exact semantics of lastChanges).

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?

Clear verb ('List') and specific resource ('cash vouchers' with parenthetical clarification 'receipts and expenses'). The 'from POHODA' scope is present. Distinguishes from siblings like pohoda_list_invoices or pohoda_create_voucher by specifying the voucher type, though it could explicitly contrast with the create_voucher sibling.

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?

Lists available filters (ID, date range, company name, last changes) which provides implied context for when to use the tool. However, lacks explicit 'when to use vs alternatives' guidance (e.g., when to use this instead of pohoda_list_accountancy or pohoda_create_voucher).

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