Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_orders_create_from_master

Creates a regular sales order (Type O) by copying a master order (Type M), with options to apply current cost or price and retain notes and user-defined fields.

Instructions

Create a Regular Order (Type O) from a Master Order (Type M).

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

Input Schema

NameRequiredDescriptionDefault
OrderNumberYesMaster order number to copy from
CustomerNumberNo
UseCurrentCostNo
UseCurrentPriceNo
CopyManualItemNotesNo
RetainUserDefinedFieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/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, and it discloses almost nothing beyond the copy direction. It doesn't say what fields are carried over versus reset, whether the copy is a one-time snapshot or a persistent link, what permissions are required, or what happens to the master order.

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?

A single front-loaded sentence with zero filler and no redundancy. It is efficient, but its brevity is partly the cause of the gaps in the other dimensions rather than a sign of a tight, complete definition.

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 six-parameter mutation tool with no annotations, no output schema, and 17% schema coverage, the description is substantially under-specified. An agent could guess the core action but could not confidently set the five boolean/identifier options or predict the result.

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

Parameters2/5

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

Schema description coverage is only 17% – only OrderNumber is documented, as 'Master order number to copy from'. The five other parameters (CustomerNumber, UseCurrentCost, UseCurrentPrice, CopyManualItemNotes, RetainUserDefinedFields) get no explanation in either the schema or the description, despite being the knobs that determine what the copied order looks like.

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 ('Create') and two specific resources ('Regular Order (Type O)' from 'Master Order (Type M)'), which is far more precise than a generic create. The 'from a Master Order' clause also implicitly separates it from the sibling customer_orders_create, though it never names that sibling or states the distinction outright.

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 when-to-use guidance, no mention of when to prefer customer_orders_create over this copy-based variant, and no prerequisites or exclusions. The agent must infer the scenario entirely from the phrase 'from a Master Order'.

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