Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_orders_delete

Deletes a specific customer order by its order ID in Macola 10, removing unwanted or outdated orders from the system.

Instructions

Deletes the specific Customer Order.

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_orders_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrder ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.8/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 behavioral burden. It signals a destructive operation but says nothing about permanence, whether child order lines are cascaded, permission requirements, or whether any confirmation or precondition exists.

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?

It is a single short sentence with no redundancy, but it is not front-loaded with actionable context and the phrase "the specific" is wasted words. Brevity here reflects under-specification rather than disciplined editing.

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 destructive mutation with no annotations and no output schema, the definition is too thin: it omits cascade effects, irreversibility, error behavior, and any usage constraints an agent needs before invoking it.

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 description coverage is 100% with a single documented 'id' property, so the schema already explains the parameter. The description adds no meaning such as format, source of the ID, or where to obtain valid IDs.

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 and resource ("Deletes ... Customer Order"), so an agent can tell it targets an order rather than an order line or purchase order. However, "the specific" is vague filler and there is no explicit contrast with siblings like customer_order_lines_delete or purchase_orders_delete.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as customer_orders_update or a credit-hold route. The agent must infer entirely whether deletion is the right action versus a status change.

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