Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_locations_find

Find inventory location entries to check item quantities at specific locations, with filters for item number and location.

Instructions

Find Inventory Location entries (item quantities at specific locations).

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_locations_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.6/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 read-only vs mutating behavior, pagination, result ordering, or what countOnly/totalCount do to the response. The only behavioral content is the parenthetical explaining what a location entry represents, which is useful but far from sufficient.

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

Conciseness3/5

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

One front-loaded sentence with no wasted words, but the brevity reflects under-specification rather than disciplined concision for an 11-parameter tool. There is no structure to separate purpose from parameter or behavior guidance because none is given.

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

Completeness2/5

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

With 11 optional parameters, no annotations, and no output schema, the description should explain at least the filtering and paging model, but it does not. It is adequate for identifying the resource and inadequate for invoking the tool correctly.

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

Parameters2/5

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

All 11 parameters have zero schema description coverage, and the description never names or explains any of them. The mention of 'item quantities' and 'locations' faintly hints at the ItemNumber and Location filters, but page, skip, order, fields, distinct, pageSize, countOnly, totalCount, and division are entirely undefined anywhere.

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 ('Find') and resource ('Inventory Location entries') and adds a parenthetical defining what an entry is ('item quantities at specific locations'), so an agent understands the record type. It does not differentiate from the sibling inventory_locations_get, leaving the find-vs-get distinction to inference from names alone.

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 guidance on when to use this tool versus inventory_locations_get or the other *_find siblings, and no prerequisites, exclusions, or typical query scenarios are mentioned. The agent must infer that this is the list/search variant purely from the name.

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