Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_orders_update

Update an existing customer order with supplied fields, including status, shipping, billing, and contact details. Providing comments replaces all previous order comments.

Instructions

Updates the specified Customer Order with the data provided. If CustomerOrderComments is provided, all previous comments will be replaced.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
StatusNo
TaxCodeNo
HoldCodeNo
ShipDateNo
BillToZipNo
JobNumberNo
OrderDateNo
OrderTypeNo
ShipToZipNo
BillToCityNo
RowVersionNo
ShipToCityNo
ShipToNameNo
BillToStateNo
ContactNameNo
OrderNumberNo
ShipToStateNo
ShipViaCodeNo
TaxScheduleNo
CommentLine1No
CommentLine2No
CommentLine3No
BillToCountryNo
FreightAmountNo
ShipToCountryNo
CustomerNumberNo
DiscountPercentNo
SalespersonNumberNo
UserDefinedField1No
UserDefinedField2No
UserDefinedField3No
UserDefinedField4No
UserDefinedField5No
BillToAddressLine1No
BillToAddressLine2No
BillToCustomerNameNo
ContactPhoneNumberNo
FreightPaymentCodeNo
ShipToAddressLine1No
ShipToAddressLine2No
ContactEmailAddressNo
MiscellaneousAmountNo
PurchaseOrderNumberNo
BillToCustomerNumberNo
AccountsReceivableTermsCodeNo
CustomerAlternateAddressCodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.6/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 disclosure burden, yet it only discloses one behavior: that CustomerOrderComments replaces all previous comments. It does not say whether this is a partial or full replacement update for the 46 other fields, does not explain the presence/role of RowVersion for optimistic concurrency, and does not state permission requirements or error behavior for mutations.

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?

Two short sentences with no filler, and the destructive comment-replacement warning is placed after the core purpose, which is reasonable. The brevity is appropriate in form; the problem is under-specification rather than verbosity.

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 46-parameter mutation tool with no annotations and no output schema, the description is far too thin: it leaves update semantics, concurrency handling, and identifier requirements unexplained. The single behavioral note about comments is the only substantive content relative to a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 46 parameters, and the description compensates for none of them beyond a vague 'with the data provided.' Worse, the only field it names, CustomerOrderComments, does not exist in the input schema (which instead exposes CommentLine1-3), so the one piece of parameter guidance given is not actionable.

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: 'Updates the specified Customer Order.' It is clearly distinguishable from customer_orders_create or customer_orders_delete by the verb alone, but it never names a sibling or explains how it differs from customer_orders_update-adjacent tools such as customer_order_lines_update.

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 explicit guidance on when to use this tool, which identifier selects the order to update (OrderNumber, CustomerNumber, or RowVersion), or what prerequisites exist. An agent must infer everything from the tool name, and there are no stated exclusions or alternatives.

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