Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_items_get

Fetches details for a specific inventory item using its item number ID, enabling lookups, validation, and order workflow checks.

Instructions

Get the Inventory Item for a particular entry by specifying its item number 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_items_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesItem number/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 supplied, so the description carries the full disclosure burden, yet it says nothing about permissions required, behavior when the ID does not exist, whether a single object or error is returned, or any rate/consistency characteristics. Only the read nature of 'Get' is conveyed, which the name already implies.

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?

A single front-loaded sentence with no filler, though 'for a particular entry' is slightly redundant with 'item number ID' and could be trimmed. Structure is otherwise efficient.

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 simple one-parameter getter with no output schema, the description is minimally sufficient to invoke it correctly, but it leaves the agent guessing about return shape and not-found behavior. With no annotations to back it up, a bit more behavioral text would be warranted.

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 coverage is 100% for the single required 'id' parameter, so the schema already documents the item number/ID, and the description merely restates it. Baseline 3 applies since the description adds no format, example, or validation detail beyond the schema.

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?

States a specific verb+resource ('Get the Inventory Item') plus the lookup key ('item number ID'), which clearly separates it from the *_find siblings by implying a single-record exact-ID retrieval. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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?

The phrase 'by specifying its item number ID' implies this is the tool for a known-ID lookup while search-style siblings cover other cases, but the description never says when to prefer this over inventory_items_find or what to do if the ID is unknown. Usage is inferable rather than stated.

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