Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_order_lines_create

Creates a new customer order line in Macola 10, letting MCP clients add item, quantity, pricing, and delivery details to an existing order.

Instructions

Creates a new Customer Order Line.

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

Input Schema

NameRequiredDescriptionDefault
LineTypeNo
LocationNo
UnitCostNo
IsTaxableNo
OrderTypeNo
UnitPriceNo
ItemNumberNo
LineNumberNo
RowVersionNo
OrderNumberNo
PromiseDateNo
RequestDateNo
TaxScheduleNo
UnitOfMeasureNo
CustomerNumberNo
DiscountPercentNo
QuantityOrderedNo
ItemDescription1No
ItemDescription2No
RequiredShipDateNo
UserDefinedField1No
UserDefinedField2No
UserDefinedField3No
UserDefinedField4No
UserDefinedField5No

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 behavioral burden, yet it discloses nothing about side effects, required permissions, whether the parent order must exist, or what happens on duplicate LineNumber. For a mutation tool with 25 parameters this is a critical gap.

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 contains no filler, but its brevity reflects under-specification rather than economy. There is no structure, no front-loaded detail, and nothing an agent can act on beyond the tool name.

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?

Given 25 parameters, no annotations, no output schema, and no required-field information, the description is far too thin to support correct invocation. An agent cannot determine which fields are mandatory or how the created line is identified in the response.

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 25 parameters, and the description compensates for none of it. Fields like LineType, OrderType, RowVersion, TaxSchedule, and the five UserDefinedField slots are entirely unexplained, and the fact that zero parameters are marked required is never addressed.

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 'Creates a new Customer Order Line' only restates the tool name customer_order_lines_create, converting the identifier into prose. It does not distinguish this tool from siblings such as customer_orders_create or purchase_order_lines_create, nor does it say what a 'line' comprises.

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 mention of prerequisites (e.g. that an existing order identified by OrderNumber is presumably required), and no routing to alternatives like customer_order_lines_update or customer_order_lines_find. The agent must infer everything from the name alone.

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