Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

shop_floor_orders_find

Find manufacturing work orders by order number, item, status, location, division, or type to review shop floor order data. Filter, paginate, and count matching orders for production tracking.

Instructions

Find Shop Floor Orders (manufacturing work orders).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
OrderTypeNo
countOnlyNo
ItemNumberNo
totalCountNo
OrderNumberNo
OrderStatusNo
OrderLocationNo

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 burden, yet it says nothing about read-only behavior, pagination defaults, result caps, or sort behavior despite exposing page/skip/order/pageSize/totalCount parameters. The only behavioral signal is the implicitly read-only verb 'Find', which comes from the name rather than the prose.

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 filler, so there is no wasted wording. But the brevity is under-specification rather than economy for a tool with 14 unfiltered parameters.

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?

With 14 optional parameters, zero schema descriptions, no annotations, and no output schema, the definition provides nothing an agent needs to construct a correct query or interpret results. This is the least-documented possible form of an otherwise complex query tool.

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 14 parameters, and the description adds no meaning for any of them. Undocumented items like 'distinct', 'fields', 'countOnly', 'totalCount', 'OrderStatus', and 'OrderLocation' leave the agent guessing at filter semantics and value formats.

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 verb 'Find' plus resource 'Shop Floor Orders' states the basic operation, and the parenthetical '(manufacturing work orders)' usefully disambiguates the domain term. However, it gives no indication of how this differs from the sibling 'shop_floor_orders_get' or what 'find' means in terms of filtering and result sets.

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 when-to-use guidance, no mention of alternatives such as 'shop_floor_orders_get' or 'customer_orders_find', and no stated preconditions. The agent is left to infer that this is a list/search operation from the verb alone.

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