Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_list_stock

Export inventory items from POHODA accounting software with filters for ID, code, name, store, or recent changes.

Instructions

Export stock/inventory items from POHODA with optional filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoStock item ID
codeNoStock code (supports wildcards *)
nameNoStock item name
storeNoStore name filter
lastChangesNoOnly items changed after this date

Implementation Reference

  • The handler and registration for 'pohoda_list_stock' tool. It constructs a XML request to list stock items from POHODA and processes the response.
    server.tool(
      "pohoda_list_stock",
      "Export stock/inventory items from POHODA with optional filters",
      {
        id: z.number().optional().describe("Stock item ID"),
        code: z.string().optional().describe("Stock code (supports wildcards *)"),
        name: z.string().optional().describe("Stock item name"),
        store: z.string().optional().describe("Store name filter"),
        lastChanges: z.string().optional().describe("Only items changed after this date"),
      },
      async (params) => {
        try {
          const xml = buildExportRequest(
            { ico: client.ico },
            "lst:listStockRequest",
            NS.lStk,
            "lst:requestStock",
            (req) => {
              const hasFilter = Object.values(params).some((v) => v != null);
              if (!hasFilter) return;
              const ftr = req.ele(NS.ftr, "ftr:filter");
              if (params.id != null) ftr.ele(NS.ftr, "ftr:id").txt(String(params.id));
              if (params.code) ftr.ele(NS.ftr, "ftr:code").txt(params.code);
              if (params.name) ftr.ele(NS.ftr, "ftr:name").txt(params.name);
              if (params.store) ftr.ele(NS.ftr, "ftr:store").ele(NS.typ, "typ:ids").txt(params.store);
              if (params.lastChanges) ftr.ele(NS.ftr, "ftr:lastChanges").txt(toIsoDate(params.lastChanges));
            },
          );
          const resp = parseResponse(await client.sendXml(xml));
          const data = extractListData(resp);
          return jsonResult("Stock items", 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 but fails to mention critical traits such as pagination behavior, default result limits, date format expectations for the 'lastChanges' parameter, or whether 'Export' implies a file download or structured data return. The description only implies a read-only operation through the word 'Export'.

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?

The description is a single, efficient sentence of nine words that places the primary action ('Export') at the beginning. While appropriately front-loaded and free of verbosity, its extreme brevity contributes to underspecification in other dimensions, though it does not contain wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of 5 optional parameters, zero required parameters, no output schema, and no annotations, the description is insufficiently complete. It fails to specify the output format, pagination controls, or the behavior when invoked without parameters (e.g., whether it returns all stock items or requires at least one filter).

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 schema has 100% description coverage for its 5 parameters, establishing a baseline of 3. The description adds marginal value by contextualizing the parameters collectively as 'optional filters,' but does not augment the schema with additional semantic details like date formats, wildcard usage examples, or the relationship between 'id' and other filter fields.

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 clearly identifies the action ('Export'), the resource ('stock/inventory items'), and the source system ('POHODA'). However, it does not explicitly differentiate from the sibling tool 'pohoda_list_movements' or clarify that this is a data retrieval operation as opposed to file generation, which would help distinguish it from potential export-to-file utilities.

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?

The phrase 'with optional filters' provides minimal implicit guidance about the parameters, but there is no explicit guidance on when to use this tool versus 'pohoda_list_movements', when to apply specific filters versus fetching all items, or prerequisites like required permissions.

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