Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

standard_routing_create

Creates a new standard routing record for an item in Macola 10, including routing number, lot size, lead times, and overlap settings.

Instructions

Creates a new Standard Routing.

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

Input Schema

NameRequiredDescriptionDefault
ItemNumberNo
OverlapCodeNo
UserDefined1No
UserDefined2No
UserDefined3No
UserDefined4No
UserDefined5No
FixedLeadTimeNo
RoutingNumberNo
OverlapQuantityNo
StandardLotSizeNo
IsDefaultRoutingNo
VariableLeadTimeNo
OverlapPercentageNo
IncrementOperationByNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description bears the full burden for a 15-parameter mutation tool, and it discloses nothing. It does not state required fields, default values, validation or overlap rules, whether IsDefaultRouting flips an existing default, or what happens on conflicting RoutingNumber/ItemNumber.

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

Conciseness2/5

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

The single sentence is short but is under-specification rather than conciseness; there is no front-loaded scope, no parameter summary, and no structure at all. It wastes the only sentence available on a restatement of the name.

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 tool with 15 undocumented parameters, zero required fields declared, no annotations, and no output schema, the description provides nothing an agent needs to invoke it correctly. It is far below the minimum needed for a create operation of this complexity.

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 15 parameters, and the description mentions none of them. Terms like OverlapCode, OverlapQuantity vs OverlapPercentage, IncrementOperationBy, FixedLeadTime/VariableLeadTime, and the five UserDefined slots are left entirely undefined for the agent.

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

Purpose2/5

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

"Creates a new Standard Routing" only restates the tool name (standard_routing_create) as a sentence. It names the verb and resource but says nothing about what a Standard Routing is, what the resulting record contains, or how it differs from the sibling create tools or from standard_routing_get/find beyond the obvious create-vs-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 when-to-use guidance: no prerequisites (e.g. whether an ItemNumber must already exist), no conditions distinguishing this from standard_routing_find/get, and no note on whether a default routing should be created here or via an update path. Usage is only weakly implied by the word "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