Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

standard_routing_find

Find manufacturing routing templates by item number, routing number, or division to retrieve standard routing data.

Instructions

Find Standard Routings (manufacturing routing templates).

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": "standard_routing_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
ItemNumberNo
totalCountNo
RoutingNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, yet it only says the tool finds routing templates. It does not disclose read-only behavior, pagination semantics, returned data shape, or permission requirements, which matters for an 11-parameter query tool.

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?

The description is a single, front-loaded sentence with no wasted words. Its brevity is appropriate structurally, though it leaves substantial gaps that are better assessed under contextual completeness and parameter semantics.

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 tool with 11 optional parameters, no annotations, no output schema, and zero schema description coverage, the definition is far too thin. It establishes the resource being found but omits parameter meanings, filtering guidance, and behavioral details needed to invoke the tool confidently.

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?

The schema has 11 parameters with 0% description coverage, and the description mentions none of them. It provides no meaning for pagination fields, RoutingNumber, ItemNumber, division, countOnly, or other parameters, so the agent gets no semantic help beyond the raw schema names.

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 uses a specific verb, "Find," and a specific resource, "Standard Routings," with a helpful parenthetical defining them as manufacturing routing templates. It clearly distinguishes the operation from siblings like standard_routing_create and standard_routing_get through its wording, though it does not explicitly name them.

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?

The description provides no guidance on when to use this find operation versus standard_routing_get or other find tools. It does not mention filtering, pagination, or any exclusions or prerequisites, leaving the agent to infer usage from the name 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