Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

purchase_orders_create

Create a new purchase order in Macola with vendor, order, shipping, tax, and comment details through the MCP server.

Instructions

Creates a new Purchase Order.

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

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

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 and discloses nothing: not the permission or auth needs, not which of the 22 fields are required or defaulted, not what the created record looks like, not whether the operation is idempotent. For a mutation tool with 22 parameters this is a complete disclosure failure.

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?

Technically a single short sentence, but the brevity is under-specification rather than economy; nothing is front-loaded because there is nothing to front-load. The one sentence earns its place only by naming the resource.

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 22 undocumented parameters, zero required fields, no annotations, and no output schema, the description is nowhere near complete. An agent cannot call this correctly without guessing at field semantics and required data.

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 (ID, RowVersion, FOBCode, BuyerPlanner, five UserDefinedFieldN entries, and so on), and the description adds no meaning for any of them. Fields like RowVersion (likely a concurrency token) and Type/Status (likely enums) are entirely uninterpretable from the definition.

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?

'Creates a new Purchase Order' restates the tool name purchase_orders_create almost verbatim and adds no scope, no distinguishing detail versus siblings such as purchase_order_lines_create or customer_orders_create. It is not misleading, but it is tautological rather than informative.

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?

No when-to-use guidance at all: nothing says when a purchase order should be created directly versus through a related flow, no prerequisites, no mention of the sibling update/find/get tools, and no exclusions. The agent must infer everything from the tool name.

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