Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_order_lines_delete

Deletes a specific customer order line by its ID, removing that line from a Macola order when it is no longer needed.

Instructions

Deletes the specific Customer 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": "customer_order_lines_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrder 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 provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond the verb. It does not say whether the delete is permanent, whether it cascades to related records or alters order totals, what permissions are required, or how failure (e.g., an invalid or already-deleted ID) is reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with zero padding, so nothing is wasted. However, the terseness crosses into under-specification rather than efficient communication; 'specific' adds no discriminating meaning.

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?

The tool is simple and the single required parameter is fully documented in the schema, so an agent can invoke it correctly. What remains missing is any statement about the consequences of a destructive call or the expected outcome, which matters given the absence of annotations and an output schema.

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?

With a single parameter and 100% schema description coverage, the schema already documents 'id' as the order line ID to delete. The description adds no format, source, or lookup guidance beyond that, so the baseline of 3 applies.

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 names a specific verb (Deletes) and resource (Customer Order Line), so the operation is unambiguous. It does not distinguish itself from close siblings such as purchase_order_lines_delete or customer_orders_delete, but the name-plus-description pairing leaves little doubt about the target entity.

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 use this versus customer_order_lines_update, customer_order_lines_get, or the parent-level customer_orders_delete. No prerequisites, no note that the line must exist, and no statement about when deletion is inappropriate.

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