Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

shop_floor_orders_get

Retrieve a specific Shop Floor Order by ID to view its production details and status.

Instructions

Get the Shop Floor Order for a particular entry by specifying its ID.

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": {
      "id": "<id>"
    },
    "name": "shop_floor_orders_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesShop floor order ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 does not meet it. It never states that this is a read-only operation, what happens when the ID does not exist, whether permissions are required, or what the response contains.

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

Conciseness4/5

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

One short sentence with no filler, and the key requirement (the ID) is placed at the end where it reads naturally. Nothing is redundant, though nothing is front-loaded beyond the verb and resource.

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

Completeness3/5

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

For a simple single-parameter getter with no output schema, the description is minimally sufficient to invoke the tool correctly. It is incomplete on return shape and failure behavior, which matters more here because no annotations or output schema cover those gaps.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage ('Shop floor order ID'), so the schema already does the work. The description's 'by specifying its ID' adds no format, source, or validation detail beyond it, making the baseline 3 appropriate.

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?

States a specific verb (Get) and resource (Shop Floor Order) plus the lookup key (ID), so the agent knows exactly what it retrieves. It does not distinguish itself from the sibling shop_floor_orders_find, leaving the get-vs-find boundary to be inferred from names alone.

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

Usage Guidelines3/5

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

The phrase 'by specifying its ID' implies this is the path when the ID is already known, which weakly contrasts with a search-style sibling. There is no explicit when-to-use or when-not-to-use statement, and no mention of what to do if the ID is unknown.

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