Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_transaction_request

Create issue or receipt inventory transactions in Macola 10 by submitting item, quantity, location, and date details to record stock movements accurately.

Instructions

Request a new Inventory Transaction. Only Issue and Receipt types are currently supported.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "TransactionType": "<TransactionType>"
    },
    "name": "inventory_transaction_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
CommentNo
JournalNo
Comment2No
LocationNo
UnitCostNo
ItemNumberNo
OrderNumberNo
VendorNumberNo
CustomerNumberNo
DocumentSourceNo
TransactionDateNo
TransactionTypeYesType: Issue or Receipt
DocumentOrderNumberNo
TransactionQuantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/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 behavioral burden and only discloses the supported transaction types. It does not explain whether this creates a pending request, what side effects occur, whether approval is required, or what happens for Issue versus Receipt.

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

Conciseness5/5

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

The description is two front-loaded sentences with no filler. The operation is stated first, followed by the supported-type constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter mutation tool with no annotations and no output schema, the definition is far too sparse. It identifies the operation and supported types but leaves most parameter meanings, request lifecycle, and return behavior unexplained.

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 14 parameters with only 7% schema description coverage, and the description does not explain the roles of Comment, Journal, Location, UnitCost, ItemNumber, OrderNumber, VendorNumber, CustomerNumber, DocumentSource, TransactionDate, DocumentOrderNumber, or TransactionQuantity. Its only parameter-related content restates the TransactionType values already present in the schema.

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 states a specific verb and resource: "Request a new Inventory Transaction." It is distinguishable from the mostly find/get sibling tools, though it does not explicitly contrast itself with alternatives.

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?

It gives one useful constraint: only Issue and Receipt transaction types are supported. However, it provides no when-to-use guidance, prerequisites, or comparison to other transaction-related actions.

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