Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_stores

Export a list of stores or warehouses from the POHODA accounting system to manage inventory locations and stock data.

Instructions

Export list of stores (warehouses) from POHODA

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the pohoda_list_stores tool.
    server.tool(
      "pohoda_list_stores",
      "Export list of stores (warehouses) from POHODA",
      {},
      async () => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            "lst:listStoreRequest",
            NS.lst,
            "lst:requestStore",
          );
          const resp = parseResponse(await client.sendXml(xml));
          const data = extractListData(resp);
          return jsonResult("Stores", 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?

No annotations provided, yet description fails to clarify if 'Export' creates a persistent file (hinted by pohoda_download_file sibling) or returns data directly, nor mentions idempotency, rate limits, or permission requirements.

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?

Single 7-word sentence with zero redundancy. Front-loaded with verb and target resource, immediately conveying the operation without extraneous text.

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 zero-parameter tool in identifying the target domain, but lacks critical context regarding output format, pagination behavior, or the specific meaning of 'Export' in the POHODA system.

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?

Tool accepts zero parameters, meeting the baseline expectation for this dimension. With 100% schema coverage (trivially true for empty schema), no additional parameter semantics are required.

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?

States specific verb 'Export' and resource 'stores (warehouses)', distinguishing from siblings like pohoda_list_invoices or pohoda_list_stock. Minor ambiguity whether 'Export' implies file creation or simple data retrieval.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., pohoda_list_stock) or prerequisites for invocation. No filtering constraints mentioned despite zero parameters implying a full export.

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