Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_delete_order

Delete an order from POHODA accounting software by specifying its ID. This tool removes order records to maintain accurate data management.

Instructions

Delete an order from POHODA by ID. Requires the order ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOrder ID to delete (required)

Implementation Reference

  • The handler and registration logic for the 'pohoda_delete_order' tool. It uses buildImportDoc to create a deletion XML request containing an actionType set to 'delete' and a filter with the ID, then sends it to the POHODA client.
    server.tool(
      "pohoda_delete_order",
      "Delete an order from POHODA by ID. Requires the order ID.",
      {
        id: z.number().describe("Order ID to delete (required)"),
      },
      async (params) => {
        try {
          const xml = buildImportDoc({ ico: client.ico }, (item) => {
            const ord = item.ele(NS.ord, "ord:order").att("version", "2.0");
            const actionType = ord.ele(NS.ord, "ord:actionType");
            const del = actionType.ele(NS.ord, "ord:delete");
            const filter = del.ele(NS.ftr, "ftr:filter");
            filter.ele(NS.ftr, "ftr:id").txt(String(params.id));
          });
          const response = await client.sendXml(xml);
          const result = extractImportResult(parseResponse(response));
          return result.success ? ok(`Order deleted successfully. ${result.message}`) : err(result.message);
        } 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, so description carries full burden. States 'Delete' but fails to disclose irreversibility, side effects (impact on inventory/accounting), or business rules (e.g., cannot delete invoiced orders). Minimal safety disclosure for a destructive ERP operation.

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?

Two short sentences, front-loaded with action. Second sentence is slightly redundant with schema's 'required' field, but overall efficient and readable.

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?

Inadequate for an ERP delete operation. No output schema handling, no mention of POHODA-specific constraints (e.g., deletion only allowed for draft orders), success/failure behavior, or idempotency. Missing critical business context for financial data deletion.

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 has 100% coverage with 'Order ID to delete (required)'. Description adds 'Requires the order ID' which is redundant with schema constraints. Baseline score appropriate since schema fully documents the single parameter.

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?

Clear specific verb (Delete) + resource (order) + system context (POHODA). Explicitly distinguishes from sibling delete tools (delete_invoice, delete_stock, etc.) by specifying 'order'.

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?

Only states the obvious parameter requirement ('Requires the order ID'). No guidance on when to use vs. alternatives, prerequisites (e.g., order status checks), or warnings about deletion constraints typical in ERP systems.

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