Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_orders_remove_credit_hold

Removes a customer order from credit hold by specifying its order type and order number, allowing the order to proceed past credit review.

Instructions

Attempts to remove a Customer Order from credit hold status, given the OrderType and OrderNumber.

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": {
      "OrderType": "<OrderType>",
      "OrderNumber": "<OrderNumber>"
    },
    "name": "customer_orders_remove_credit_hold"
  }
}

Input Schema

NameRequiredDescriptionDefault
OrderTypeYesOrder type (e.g. O)
OrderNumberYesOrder number to remove from credit hold

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?

With no annotations, the description carries the full behavioral burden. It implies a mutating state change and hints that it may not succeed via 'Attempts', but it omits permission requirements, reversibility, side effects, idempotency, and what happens when the order is not on credit hold.

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?

The description is a single front-loaded sentence with no wasted wording. The word 'Attempts' usefully signals non-guaranteed success, though the brevity leaves behavioral gaps.

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 mutating operation with no annotations and no output schema, the description is too thin. It does not tell the agent what success or failure looks like, whether the operation is safe to retry, or what preconditions must hold 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%, so both parameters are already documented in the input schema. The description only repeats that OrderType and OrderNumber identify the order, adding no format, validation, or lookup semantics beyond the schema.

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 operation: removing a Customer Order from credit hold, identified by OrderType and OrderNumber. It distinguishes itself from generic order update/create/delete siblings by naming the credit-hold state transition.

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?

It does not explain when to use this tool versus customer_orders_update or any other alternative, nor does it state prerequisites such as the order actually being on credit hold or required permissions. Usage is only implied by the tool name and description.

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