Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_kits_find

Find inventory kit records in Macola 10 by item number, division, and pagination filters to support kit lookups and reporting.

Instructions

Find Inventory Kit data.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
ItemNumberNo
totalCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.8/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 provides none of it: no statement about read-only safety, pagination defaults, result ordering, or whether countOnly/totalCount change the response shape. For a 10-parameter query tool, this is a critical gap.

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 not bloated, but at four words it is under-specified rather than concise, and there is no front-loaded structure an agent could use to plan a call. Brevity here reflects missing content, not efficiency.

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?

A tool with 10 optional query parameters, no annotations, and no output schema needs substantial explanation of filtering, pagination, and return shape. The description provides none, leaving the definition inadequate for correct invocation.

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 10 parameters, including non-obvious ones like 'distinct', 'fields', 'division', and 'countOnly'. The description adds no meaning whatsoever beyond the parameter names, leaving paging, projection, and filtering semantics entirely undocumented.

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?

The description states a verb ('Find') and a resource ('Inventory Kit data'), which is enough to know it retrieves inventory kits. It does not, however, distinguish this from the sibling inventory_kits_get, so an agent cannot tell from the text alone whether 'find' implies list/search semantics versus a single-record fetch.

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 guidance on when to use this tool versus inventory_kits_get or the other *_find siblings, no prerequisites, and no note about what the returned set represents. The agent must infer list-vs-get semantics purely from naming convention.

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