Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_order_lines_update

Updates a specified customer order line in Macola 10 with the provided price, quantity, discount, and shipping date data.

Instructions

Updates the specified Customer Order Line with the data provided.

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

Input Schema

NameRequiredDescriptionDefault
IDNo
OrderTypeNo
UnitPriceNo
LineNumberNo
RowVersionNo
OrderNumberNo
PromiseDateNo
DiscountPercentNo
QuantityOrderedNo
RequiredShipDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.4/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 disclosure burden and delivers almost nothing: it does not say whether this is a partial or full replacement update, what happens to omitted fields, whether RowVersion is required for optimistic concurrency, or what permissions are needed. The word "Updates" implies mutation but none of the risky semantics of a 10-parameter write are described.

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

Conciseness3/5

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

It is a single short sentence that is front-loaded with the verb and resource, which is good structure. However, the closing clause "with the data provided" is pure filler, and concision here reflects under-specification rather than economy.

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 mutation tool with 10 undocumented parameters, zero required fields, no annotations, and no output schema, the definition leaves nearly everything important unspecified. An agent cannot determine required inputs, update semantics, or concurrency handling from this description.

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 10 parameters, and the description compensates with nothing — it does not even mention a single field name, let alone the meaning of ID, RowVersion, DiscountPercent, or the date fields. An agent has no basis beyond field names to decide what to send or which are mandatory.

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 ("Updates") and resource ("Customer Order Line"), so the agent knows the operation type and target entity. It offers no differentiation from close siblings such as customer_order_lines_create or customer_order_lines_delete, and the trailing "with the data provided" adds no information.

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 guidance on when to use this versus create, delete, find, or get on the same resource, nor on prerequisites such as needing an existing line ID or a valid RowVersion. The description never states when not to use it or what conditions make the update valid.

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