Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_bins_get

Retrieve inventory bin details by ID to look up storage location information for Macola inventory records.

Instructions

Get the Inventory Bin 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_bins_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInventory bin 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 read of one record; it says nothing about error behavior for missing/invalid IDs, required permissions, or what the response contains. For a bare read tool this is thin but not misleading.

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 the key action and selector stated immediately. The phrase 'for a particular entry' is slightly redundant with 'by specifying its ID', but the wording 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 one-parameter read tool with no output schema, the description covers the essentials of what is fetched and how it is identified. It leaves the return shape and edge-case behavior unaddressed, which is an acceptable but not complete treatment at this complexity.

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?

There is a single parameter with 100% schema description coverage ('Inventory bin ID'), so the schema already fully documents it. The description's 'by specifying its ID' restates the schema rather than adding format, source, or lookup semantics, which lands at the baseline of 3.

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 uses a clear verb+resource pair ('Get the Inventory Bin information') and scopes it to a single entry identified by ID. It does not differentiate itself from the sibling inventory_bins_find, which is the natural confusion point, 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?

Retrieving 'a particular entry by specifying its ID' implicitly signals single-record lookup versus the find-style siblings, but the description never says when to choose this over inventory_bins_find or what happens 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