Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

shop_floor_orders_create

Creates a new Shop Floor Order (manufacturing work order) to start production tracking, assign job numbers, and record order details.

Instructions

Creates a new Shop Floor Order (manufacturing work 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": "shop_floor_orders_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
DueDateNo
JobNumberNo
OrderTypeNo
ItemNumberNo
OrderNumberNo
OrderStatusNo
CompleteDateNo
StartingDateNo
IssueLocationNo
OrderLocationNo
OrderQuantityNo
RoutingNumberNo
UserDefinedField1No
UserDefinedField2No
UserDefinedField3No
UserDefinedField4No
UserDefinedField5No
SourceOrderNumberSalesOrderNo

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 supplied, so the description carries the full behavioral burden and discharges almost none of it. It does not say what identifies a unique order (OrderNumber? JobNumber?), what happens on duplicates, what permissions are needed, or which fields are mandatory despite the schema declaring zero required parameters for a create operation.

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 free of waste, but at this length the brevity reflects under-specification rather than discipline. It is efficient without being informative.

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 18 undocumented parameters, no annotations, and no output schema, the description is drastically incomplete. An agent cannot determine required inputs, identifier semantics, or expected results for a manufacturing work-order creation from this sentence.

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?

All 18 parameters have 0% schema description coverage and the description mentions none of them. It gives no meaning for DueDate vs StartingDate vs CompleteDate, no indication of valid OrderType or OrderStatus values, and no explanation of the UserDefinedField1-5 slots, so an agent has nothing to reason from beyond bare property 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 description pairs the verb 'Creates' with the resource 'Shop Floor Order' and adds a clarifying gloss, '(manufacturing work order)'. That gloss is the only real added information, since the tool name shop_floor_orders_create already states the same thing; it distinguishes nothing about how this differs from shop_floor_orders_find or shop_floor_orders_get beyond the obvious create/read split.

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 statement of when to use this tool, no prerequisites, and no mention of the sibling create tools (customer_orders_create, purchase_orders_create) that an agent might confuse it with. Usage is only implied by the verb 'Creates'.

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