Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_items_find

Retrieve customer-specific item numbers and descriptions to match inventory records to a customer's catalog.

Instructions

Find Customer Items (customer-specific item numbers/descriptions).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
fieldsNo
distinctNo
divisionNo
historicNo
pageSizeNo
countOnlyNo
ItemNumberNo
totalCountNo
CustomerNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses nothing: no indication of whether results are paginated, whether historic/inactive records are included by default, whether any auth scope is required, or what a match on item number vs description means. 'Find' weakly implies a read, but no behavioral trait beyond that is stated.

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 contains no waste and is front-loaded, but it is under-specified rather than concise. For an 11-parameter search tool, this length leaves the agent without the information needed to call it correctly.

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?

Given eleven optional parameters, no annotations, no output schema, and zero schema coverage, the description is far too thin. Nothing tells the agent how to combine filters, what defaults apply when all parameters are omitted, or what the response contains.

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?

Eleven parameters with 0% schema description coverage, and the description explains none of them. The parenthetical loosely gestures at ItemNumber, but the paging controls (page, skip, pageSize), projection/aggregation switches (fields, distinct, countOnly, totalCount), and scoping filters (division, historic, CustomerNumber) are entirely undocumented in both the schema and the description.

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?

"Find Customer Items" states a specific verb and resource, and the parenthetical 'customer-specific item numbers/descriptions' distinguishes the resource from the sibling inventory_items_find by making clear these are customer-scoped item records rather than stock items. It stops short of routing the agent to or away from customer_items_get, so it is clear but not sibling-differentiating in an actionable way.

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 statement of prerequisites, and no mention of the obvious alternative customer_items_get. The agent must infer from the name alone whether to search here or fetch a single customer item elsewhere.

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