Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_delete_contract

Delete a contract from POHODA accounting software by specifying its unique ID. This tool removes contracts from the system when they are no longer needed.

Instructions

Delete a contract from POHODA by ID. Requires the contract ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContract ID to delete (required)

Implementation Reference

  • Implementation and registration of the 'pohoda_delete_contract' tool.
    server.tool(
      "pohoda_delete_contract",
      "Delete a contract from POHODA by ID. Requires the contract ID.",
      {
        id: z.number().describe("Contract ID to delete (required)"),
      },
      async (params) => {
        try {
          const xml = buildImportDoc({ ico: client.ico }, (item) => {
            const con = item.ele(NS.con, "con:contract").att("version", "2.0");
            const actionType = con.ele(NS.con, "con:actionType");
            const del = actionType.ele(NS.con, "con: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(`Contract 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 are provided, so the description must carry the full burden of behavioral disclosure. While 'Delete' implies destruction, the description fails to disclose that this operation is permanent, irreversible, or whether it has cascading effects on related records. For a destructive operation, this omission is significant.

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?

Appropriately brief with two short sentences. However, the second sentence ('Requires the contract ID') wastes space by repeating information already explicit in the schema's required field list and parameter description. Front-loading is adequate with the action stated first.

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 that this is a destructive operation with zero annotations and no output schema, the description is dangerously incomplete. It lacks critical safety information (irreversibility warnings), return value description (success/failure indicators), or relationship context to list_contracts (how to find the ID).

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 coverage is 100%, establishing a baseline of 3. The description adds 'Requires the contract ID,' which is redundant with the schema's 'required' constraint and the parameter description 'Contract ID to delete (required)'. No additional semantic context (e.g., ID format, where to find the ID) is provided.

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 the specific action (Delete), resource (contract from POHODA), and scope (by ID). Distinguishes from siblings like pohoda_create_contract or pohoda_delete_invoice by specifying the 'contract' resource type. Falls short of 5 because it lacks scope qualifiers (e.g., 'permanently removes') or workflow context.

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., when to delete vs. update a contract). No mention of prerequisites, state requirements (e.g., 'only drafts can be deleted'), or warnings about irreversibility. The second sentence merely restates the required parameter.

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