Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

purchase_order_lines_delete

Deletes a specific purchase order line by ID, removing it from Macola 10 purchase order data.

Instructions

Deletes the specific Purchase Order Line.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "purchase_order_lines_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPurchase order line ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a destructive mutation. It does not state that deletion is permanent, whether child records or totals are recalculated, what permissions are required, or what the response contains — all critical for an irreversible 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?

One short sentence, front-loaded with the verb. Nothing is wasted, but the brevity leaves the destructive semantics unstated.

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?

For a delete operation with no annotations and no output schema, the description is too thin — irreversibility, side effects on order totals, and required permissions are all absent.

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 single parameter has 100% schema description coverage ("Purchase order line ID to delete"), so the baseline is 3. The description adds no further meaning, such as whether the ID is the line's own ID or the parent order's, and it is fine that it does not.

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 states a specific verb and resource — it deletes one Purchase Order Line identified by ID. Among siblings such as purchase_order_lines_update and purchase_order_lines_find, the operation is unambiguous, though the description never explicitly contrasts itself with those alternatives.

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?

There is no guidance on when to delete a line versus updating or removing the whole purchase order, and no stated prerequisites such as the line being unreceived or the order being open for editing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools