Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

purchase_order_lines_update

Update a purchase order line in Macola 10 by submitting revised item, quantity, pricing, dates, or vendor details. Use it to correct or adjust existing PO line data through the MCP server.

Instructions

Updates the specified Purchase 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": "purchase_order_lines_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
IDNo
JobNumberNo
ItemNumberNo
LineNumberNo
RowVersionNo
OrderNumberNo
PromiseDateNo
RequestDateNo
TaxScheduleNo
ExpectedCostNo
VendorNumberNo
StockLocationNo
UnitOfMeasureNo
ItemDescriptionNo
QuantityOrderedNo
UserDefinedField1No
UserDefinedField2No
UserDefinedField3No
UserDefinedField4No
UserDefinedField5No
PurchasingUnitOfMeasureNo

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?

No annotations are supplied, so the description carries the full disclosure burden, yet it only implies mutation. It does not say whether omitted fields are left unchanged or cleared (critical here, since all 21 parameters are optional and none are required), nor does it explain the RowVersion concurrency requirement, permission needs, or whether updates are reversible. The only behavioral content is a restatement of the name.

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 front-loaded sentence with no wasted length, and the verb-resource structure is easy to scan. However, the phrase 'with the data provided' is pure filler, and the brevity 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 21 parameters, no required-field markers, no annotations, and no output schema, one generic sentence is far from adequate. An agent cannot determine what to pass, what will be changed, or what will come back.

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?

There are 21 parameters with 0% schema description coverage, and the description documents none of them. Key fields such as RowVersion (concurrency token), ID (line identifier), and the five UserDefinedField slots are left entirely unexplained. The phrase 'the specified Purchase Order Line' only faintly hints that an identifier is required.

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 and resource: 'Updates the specified Purchase Order Line.' This clearly distinguishes it from sibling operations like purchase_order_lines_create, _delete, _find, and _get. The trailing phrase 'with the data provided' adds no information, but the core statement is unambiguous.

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 tool versus the create, delete, or find siblings, and no prerequisites are stated. It never mentions that a line must already exist or that a lookup identifier is needed. An agent must infer all usage conditions from the tool 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