Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_settings

Export specific settings lists from POHODA accounting software, including numerical series, bank accounts, stores, and categories, for integration with MCP-compatible clients.

Instructions

Export settings/lists from POHODA. Types: numericalSeries, cashRegister, bankAccount, centre, activity, payment, store, storage, category, accountingUnit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
settingsTypeYesType of settings to export

Implementation Reference

  • The implementation of the `pohoda_list_settings` tool, which handles the request to export settings from POHODA based on the provided settingsType.
    server.tool(
      "pohoda_list_settings",
      "Export settings/lists from POHODA. Types: numericalSeries, cashRegister, bankAccount, centre, activity, payment, store, storage, category, accountingUnit",
      {
        settingsType: z.enum(settingsTypeEnum).describe("Type of settings to export"),
      },
      async (params) => {
        try {
          const cfg = SETTINGS_TYPES[params.settingsType];
          if (!cfg) return err(`Unknown settings type: ${params.settingsType}`);
    
          const xml = buildExportRequest(
            { ico: client.ico },
            cfg.listTag,
            cfg.listNs,
            cfg.requestTag,
          );
          const resp = parseResponse(await client.sendXml(xml));
          const data = extractListData(resp);
          return jsonResult(`Settings: ${params.settingsType}`, data, data.length);
        } catch (e) {
          return err((e as Error).message);
        }
      },
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Export' implies a read operation, the description does not confirm read-only safety, disclose pagination behavior, explain return format, or mention any rate limits or permission requirements for accessing these configuration lists.

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 is efficiently front-loaded with the core action ('Export settings/lists') followed by the specific type enumeration. No filler words or redundant explanations are present; every element serves a purpose.

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?

For a single-parameter tool, the description adequately covers the input domain. However, given the absence of output schema and annotations, the description lacks completeness regarding what data structure is returned and how this 'export' differs from other list operations in terms of data freshness or scope.

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 ('Type of settings to export') and the description redundantly lists the enum values. This provides clarity but adds no semantic meaning beyond the schema itself (e.g., no examples of what 'numericalSeries' or 'centre' represent in the POHODA context).

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 uses a specific verb ('Export') and resource ('settings/lists from POHODA') and enumerates the exact configuration types supported (numericalSeries, cashRegister, etc.). This distinguishes it from siblings that handle transactional entities (invoices, orders) rather than master configuration data.

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 lists the available settings types, it fails to clarify when to use this tool versus overlapping siblings like 'pohoda_list_bank' (which could conflict with 'bankAccount' type) or 'pohoda_list_stores' (which could conflict with 'store' type). No prerequisites or exclusion criteria are provided.

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