Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_bins_find

Locate inventory bin entries by item number, location, division, or other fields, with paging and count options for Macola 10 data.

Instructions

Find Inventory Bin entries.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2/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 burden, yet it says nothing about pagination, default result limits, filtering behavior, permissions, or return shape. The 11 parameters include paging and count controls (page, skip, pageSize, countOnly, totalCount) that hint at behavior the description never explains.

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 not concise in any useful sense — it is under-specified rather than efficient. There is no structure to front-load because nothing beyond the resource name is conveyed.

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 an 11-parameter query tool with no annotations, no output schema, and zero schema documentation, the definition leaves nearly everything unknown. An agent cannot determine filtering semantics, paging defaults, or result contents from this description.

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 11 parameters, and the description adds no meaning for any of them. Names like Location, distinct, fields, and countOnly are ambiguous without explanation of syntax, allowed values, or interaction between paging and totalCount.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Find Inventory Bin entries" names a specific resource (Inventory Bins) and implies a search/list operation, which is more than a bare tautology. However, it does not distinguish this from the sibling inventory_bins_get, nor does it say whether it lists, searches, or filters bins. An agent knows the domain but not the exact operation.

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

Usage Guidelines2/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 mention of when to prefer inventory_bins_get over this tool, and no stated prerequisites. The only usable signal is the generic verb "find", which weakly implies a query-style lookup rather than a single-record retrieval.

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