Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_serial_lots_find

Find inventory serial and lot records by item, location, division, or serial/lot code to retrieve Macola 10 traceability data and support stock inquiries.

Instructions

Find Inventory Serial/Lot information.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
LocationNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
ItemNumberNo
totalCountNo
SerialLotCodeNo

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 delivers none of it. It does not state whether this is a read-only query, how results are paginated, whether large result sets are truncated, or what the caller must supply to scope the search.

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 short but that is under-specification rather than conciseness. There is no structure, no front-loaded scoping rule, and nothing for the agent to act on.

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 12-parameter query tool with no annotations and no output schema, the definition supplies zero context about filtering, paging, or return shape. An agent would have to guess the meaning of most parameters before it could call this correctly.

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 12 parameters, and the description mentions no parameters at all. Critical scoping inputs like ItemNumber, SerialLotCode, Location, and division, plus paging controls (page, skip, pageSize, totalCount, countOnly) and field selection (fields, order, distinct), are entirely 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 Inventory Serial/Lot information" essentially restates the tool name inventory_serial_lots_find with the word "information" appended. It does not specify what a serial/lot record contains or how it differs from the sibling inventory_serial_lots_get, so an agent cannot separate find-vs-get semantics from the text.

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 prerequisite or context conditions, and no mention of any alternative tool. The sibling set includes both a _get counterpart and many other inventory _find tools, yet the description routes the agent nowhere.

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