Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_substitute_items_get

Fetches a substitute inventory item by ID from Macola 10 to identify replacement or alternate stock items for inventory and order workflows.

Instructions

Get the Substitute Item by 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": "inventory_substitute_items_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSubstitute item ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and delivers almost nothing: no statement about error behavior when the ID doesn't exist, permissions, or what a successful response contains. "Get" implies a read operation, but that is the only behavioral signal.

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?

A single front-loaded sentence with no wasted words. It is efficient, though its brevity borders on under-specification rather than crispness.

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 simple one-parameter lookup this is nearly adequate, but with no output schema and no annotations, the description should at minimum characterize the returned substitute-item record and not-found behavior. Those gaps are not covered anywhere else.

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?

Schema coverage is 100% and the single parameter is fully documented in the schema, so the baseline is 3. The phrase "by ID" restates the schema's meaning without adding format, source, or validation detail.

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 and resource ("Get the Substitute Item") and adds "by ID," which implicitly contrasts with the lookup/search sibling inventory_substitute_items_find. It does not explicitly name or differentiate against siblings, so it falls short of a 5.

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?

"By ID" only implies the tool requires a known identifier; there is no explicit statement of when to use this versus inventory_substitute_items_find or what to do if the ID is unknown. No exclusions or alternatives are offered.

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