Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_kits_get

Retrieve inventory kit details by ID to look up kit components and configuration for a specific Macola 10 inventory entry.

Instructions

Get the Inventory Kit 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_kits_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInventory kit 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 does not disclose what happens when the ID is invalid or not found, whether the read is safe, what fields are returned, or any permission requirements.

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 or redundancy. It is appropriately sized for a simple single-record lookup, though brevity borders on under-specification.

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 with a fully documented schema, the description covers the core intent adequately. It is missing error/not-found behavior and any indication of return content, which would matter given the absence of annotations and output schema.

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% with a single documented 'id' parameter, so baseline is 3. The description restates that the ID identifies the entry but adds no format, type, or sourcing guidance 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 and resource ('Get the Inventory Kit information') and clarifies it targets a single entry identified by ID, which implicitly contrasts with a collection-style sibling. It does not explicitly name or distinguish itself from inventory_kits_find, so it falls short of a 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 ID' implies the tool requires a known identifier, hinting at when to use it versus a search-style tool. However, there is no explicit when-to-use or when-not-to-use guidance and no mention of the find alternative.

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