Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

purchase_orders_update

Update an existing Macola purchase order with supplied details such as status, dates, vendor, shipping, and comments to keep order records current.

Instructions

Updates the specified Purchase Order 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_orders_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
IDNo
DateNo
TypeNo
StatusNo
FOBCodeNo
Comment2No
Comment3No
TermsCodeNo
RowVersionNo
ShipToCodeNo
OrderNumberNo
ShipViaCodeNo
TaxScheduleNo
BuyerPlannerNo
CurrencyCodeNo
VendorNumberNo
UserDefinedField1No
UserDefinedField2No
UserDefinedField3No
UserDefinedField4No
UserDefinedField5No
AdditionalCommentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely fails it. "Updates" implies mutation, but nothing says whether omitted fields are cleared or preserved (partial vs full replace), that RowVersion is a concurrency token that can cause the call to fail, what permissions are needed, or what is returned on success or failure.

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 and free of padding, which is structurally fine. Its brevity, though, is the product of under-specification rather than economy, so it cannot score higher.

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 22-parameter mutation tool with no annotations, no output schema, and no documented fields, this description is far too thin. An agent cannot safely call it without knowing which parameters are needed, how partial updates behave, or how concurrency via RowVersion is handled.

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 22 parameters, including non-obvious fields like RowVersion, FOBCode, TaxSchedule, and UserDefinedField1-5, and the description adds no meaning whatsoever. It does not even state that ID identifies the record to update, leaving every parameter undocumented in both schema and prose.

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

Purpose3/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"), so the agent knows this is a mutation on a purchase order. However, "with the data provided" is filler and the sentence does little more than restate the tool name; it offers no differentiation from siblings such as purchase_orders_create or purchase_order_lines_update.

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 statements, and no exclusions. The agent must infer on its own that this is for modifying an existing purchase order rather than creating or updating its lines, and nothing indicates what happens if the wrong ID is supplied.

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