Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_substitute_items_find

Find substitute inventory items for a Macola master item number, with paging and filtering, to identify alternatives when an item is unavailable or needs replacement.

Instructions

Find Substitute Items.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo
MasterItemNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no pagination behavior despite page/skip/pageSize parameters, no note on whether countOnly/totalCount change the response shape, and no indication of result limits or required filters.

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?

Two words is concise but not informative; there is no structure to speak of and nothing is front-loaded because there is no content. Brevity here reflects under-specification rather than economy.

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 10-parameter query tool with no annotations, no output schema, and no parameter documentation, the definition is wholly inadequate. An agent cannot reliably construct a correct call from it.

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?

Ten parameters with 0% schema description coverage and the description mentions none of them. MasterItemNumber in particular is the obvious key for a substitute lookup, yet nothing explains whether it is required, and the OData-style controls (order, fields, distinct, countOnly) are left undocumented.

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?

"Find Substitute Items" only restates the tool name's verb and resource; it adds no scope, no criteria, and no distinction from the sibling inventory_substitute_items_get or the other *_find tools. An agent knows roughly the domain but nothing about what a "substitute item" relation means here.

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

Usage Guidelines1/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 statement of what a substitute item is versus a kit component or related item, and no mention of the sibling get variant. The agent must guess entirely.

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