Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_addresses

Retrieve and filter address records from POHODA accounting software by ID, company name, IČO, last changes date, or code. Returns matching addresses in JSON format.

Instructions

List addresses from POHODA addressbook. Supports filtering by id, company name, IČO, last changes date, or code. Returns JSON array of matching address records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoFilter by address ID
companyNameNoFilter by company name
icoNoFilter by IČO (company ID number)
lastChangesNoFilter by last changes date (DD.MM.YYYY or YYYY-MM-DD)
codeNoFilter by address code

Implementation Reference

  • Handler function for the 'pohoda_list_addresses' tool. It builds an XML request using provided filters, sends it via the Pohoda client, parses the response, and returns the result.
    async (params) => {
      try {
        const filterParams: ListFilterParams = {
          id: params.id,
          companyName: params.companyName,
          ico: params.ico,
          lastChanges: params.lastChanges,
          code: params.code,
        };
        const xml = buildExportRequest(
          { ico: client.ico },
          "lst:listAddressBookRequest",
          NS.lAdb,
          "lst:requestAddressBook",
          (req) => applyFilter(req, filterParams)
        );
        const response = await client.sendXml(xml);
        const parsed = parseResponse(response);
        const data = extractListData(parsed);
        return jsonResult("Addresses", data, Array.isArray(data) ? data.length : 0);
      } catch (e) {
        return err((e as Error).message);
      }
    }
  • Registration of the 'pohoda_list_addresses' tool with its schema definition within the 'registerAddressTools' function.
    server.tool(
      "pohoda_list_addresses",
      "List addresses from POHODA addressbook. Supports filtering by id, company name, IČO, last changes date, or code. Returns JSON array of matching address records.",
      {
        id: z.number().optional().describe("Filter by address ID"),
        companyName: z.string().optional().describe("Filter by company name"),
        ico: z.string().optional().describe("Filter by IČO (company ID number)"),
        lastChanges: z.string().optional().describe("Filter by last changes date (DD.MM.YYYY or YYYY-MM-DD)"),
        code: z.string().optional().describe("Filter by address code"),
      },
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the return format ('JSON array of matching address records'), but fails to explicitly state the read-only/safe nature of the operation or mention pagination behavior/limits given the optional filtering.

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 and filtering capability, second specifies return format. Information is front-loaded and appropriately sized for the tool's complexity.

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 no output schema exists, the description appropriately specifies the return type ('JSON array'). For a simple filtered list operation with 5 optional parameters, it covers the essential operational context, though it could explicitly note that all parameters are optional filters.

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 a baseline of 3. The description lists the available filter fields, which mirrors the schema content but doesn't add additional semantic context (e.g., explaining IČO format, date syntax details beyond what the schema shows).

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?

Description clearly states the verb (List) and resource (addresses from POHODA addressbook), distinguishing it from siblings like pohoda_list_invoices or pohoda_create_address. The scope is immediately apparent.

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 verb 'List' implies read/search usage, but there is no explicit guidance on when to use this versus pohoda_create_address or pohoda_update_address, nor any mention of prerequisite steps like 'use this to check for existing addresses before creating'.

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