Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

purchase_order_lines_create

Creates a new purchase order line in Macola 10, capturing item, quantity, vendor, and delivery details for procurement workflows.

Instructions

Creates a new Purchase 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": "purchase_order_lines_create"
  }
}

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.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 full behavioral burden. It only implies a write operation through the word 'Creates' and says nothing about required fields, auto-generated identifiers, permissions, side effects, or the response. For a 21-parameter mutation tool, this is a severe disclosure gap.

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?

The single sentence is front-loaded and contains no wasted wording, but it is under-specified rather than genuinely concise. There is no structure to help an agent understand the operation beyond the bare statement.

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 a 21-parameter create tool with no annotations, no required fields, no output schema, and 0% schema description coverage, the description is completely inadequate. An agent cannot determine which fields to supply, what the tool returns, or how it relates to sibling creation tools.

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?

The schema has 21 parameters with 0% description coverage and zero required parameters, and the description adds no meaning for any of them. It does not explain fields like OrderNumber, LineNumber, RowVersion, or the UserDefinedField slots, leaving an agent with no guidance beyond parameter names.

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 sentence states a specific verb (creates) and resource (Purchase Order Line), so the purpose is discernible. However, it essentially expands the tool name into a sentence and provides no distinction from related creation tools such as purchase_orders_create or customer_order_lines_create.

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 header-level purchase_orders_create or the customer_order_lines_create sibling. No prerequisites, such as whether the parent purchase order must already exist, are mentioned.

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