Skip to main content
Glama
Sign In

QuailOS

by com.quailos
OverviewDiscussionsAdmin

complete_production_order

Idempotent

Mark a manufacturing production order Completed, exactly like the app's Complete button: deducts each BOM component's quantityActuallyUsed, adds quantityToProduce of the finished product, and logs inventory adjustments. Owner/admin/manager keys only. Rejects component stock going below zero unless allowNegative is true. Supports confirm (false = dry-run preview).

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": {
      "farmId": "<farmId>"
    },
    "name": "complete_production_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
farmIdYesThe unique farm ID
confirmNoSet to true to commit, false for dry-run preview
orderIdNoProduction order document ID (or use moNumber)
moNumberNoProduction order number, e.g. MO-0001 (or use orderId)
allowNegativeNoAllow component stock to go below zero (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With annotations present, the description still adds substantial context: which quantities get deducted vs. added, that inventory adjustments are logged, the authorization tier required, the rejection condition on negative stock, and the dry-run preview mode. This is exactly the beyond-annotation detail the bar asks for.

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?

A single dense paragraph front-loads the action and side effects, then layers permissions, constraints, and the dry-run flag. No filler sentences; each clause carries operational information.

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

Completeness4/5

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

Covers mutation semantics, permissions, failure conditions, and safety via dry-run — all the essentials for a 5-param mutation with no output schema. It stops short of describing what the dry-run preview actually returns, a minor gap for an agent relying on it to validate before committing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds consequence-level meaning: allowNegative governs whether the stock-floor rejection fires, and confirm=false yields a non-committing preview. It does not explain the orderId/moNumber alternative, which the schema carries alone.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Mark a manufacturing production order Completed') and immediately enumerates the exact side effects (deducts quantityActuallyUsed, adds quantityToProduce, logs adjustments). This is clearly distinguishable from siblings like create_production_order and get_production_orders.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives strong context: 'exactly like the app's Complete button', owner/admin/manager keys only, and the confirm dry-run path. It does not name an alternative tool or state explicit when-not conditions (e.g., versus adjust_inventory_stock for manual corrections), which keeps it from a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All QuailOS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources