Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_items_find

Locate inventory master item records by item number, description, category, division, or location. Filter and paginate results to find stocked finished goods and manage Macola 10 inventory data.

Instructions

Find Inventory Items (master item records).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
LocationNo
distinctNo
divisionNo
pageSizeNo
StockedFGNo
countOnlyNo
ItemNumberNo
totalCountNo
ProductCategoryNo
SearchDescriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.1/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 it discloses almost nothing. "Find" weakly implies a read-only search, but pagination behavior (page, skip, pageSize, order, distinct, countOnly, totalCount), default result size, and any filtering semantics are entirely unstated despite being central to calling this tool safely.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, and the parenthetical adds a small clarifying detail. The terseness here reflects under-specification rather than real economy, so it earns only a middling score.

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 14-parameter search tool with no annotations and no output schema, one sentence is nowhere near sufficient. An agent cannot determine how to filter, how to page, what fields are allowed, or what shape the response takes.

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 14 parameters, so the description must compensate and adds nothing. Names like StockedFG, SearchDescription, distinct, fields, totalCount, and countOnly are ambiguous without explanation, and the description never mentions that filtering, projection, pagination, or counting options even exist.

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

Purpose3/5

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

"Find Inventory Items (master item records)" names a verb and a resource, and the parenthetical clarifies the record type, so the basic purpose is intelligible. It stops short of distinguishing this from the many sibling find/get tools (inventory_items_get, customer_items_find, inventory_kits_find) or explaining what set of items is searched.

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 at all: nothing says when to prefer this over inventory_items_get, or when to reach for a related find tool like inventory_bins_find or customer_items_find. The agent must infer usage purely from the name.

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