Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_orders_create

Create a new customer order in Macola by submitting customer, order, shipping, billing, and payment details for accurate sales order entry.

Instructions

Creates a new Customer Order.

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

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

D1.5/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden and discharges none of it. It does not state required fields, side effects of creating an order, whether a credit hold or validation can block creation, what happens to the 46 optional fields when omitted, or what is returned.

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

Conciseness2/5

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

The single sentence is free of padding, but this is under-specification rather than conciseness. Nothing is front-loaded because there is nothing to front-load.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/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 zero annotation coverage, no output schema, and no field documentation, a one-clause description is completely inadequate. An agent cannot construct a valid payload or anticipate failure modes from it.

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 supplies no parameter meaning at all. Critical semantics such as OrderType, Status, HoldCode, TaxSchedule, RowVersion, or the UserDefinedField slots are entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence restates the tool name almost word for word: 'Creates a new Customer Order' adds no scope, no distinguishing detail versus siblings such as customer_orders_create_from_master, and no indication of what a 'Customer Order' comprises. The verb and resource are accurate but the statement is tautological.

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 prerequisite conditions (e.g. does a customer number need to exist first?), and no mention of the alternative customer_orders_create_from_master for order creation from a template. The agent must infer everything from the tool name.

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