Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_serial_lots_get

Fetch inventory serial and lot information by ID to verify tracking details for a specific stock entry.

Instructions

Get the Inventory Serial/Lot information for a particular entry by specifying its ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "inventory_serial_lots_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSerial/lot ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/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. It conveys only that this is a lookup by ID; it says nothing about behavior when the ID does not exist, permission requirements, or what the returned "information" comprises.

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

Conciseness4/5

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

One front-loaded sentence with no padding and no redundancy. It is efficient, though the phrase "for a particular entry" is slightly vague filler that could have been spent on differentiating from the find sibling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool this is close to adequate, but with no output schema the description never characterizes the returned "information" (fields, cardinality), and with no annotations it does not cover error or safety behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter is already documented as "Serial/lot ID". The phrase "by specifying its ID" restates the schema without adding format, source, or constraint details, so the baseline of 3 applies.

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?

The description states a specific verb (Get) and resource (Inventory Serial/Lot information) scoped to a single entry identified by ID, which is clear enough to act on. It does not, however, distinguish itself from the sibling inventory_serial_lots_find, leaving the retrieval-vs-search distinction implicit.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"By specifying its ID" implies the precondition that the caller already has a serial/lot ID, which is a weak signal of when to use it. There is no statement of when not to use it or that inventory_serial_lots_find should be used when the ID is unknown.

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