Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

locations_find

Find warehouse and inventory locations using filters like location code, division, and stocking status to narrow results. Supports paging, field selection, ordering, and count-only queries.

Instructions

Find Locations (warehouse/inventory locations). When StockingFilter is true, filtering applies to both Location and InventoryLocation.

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": "locations_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo
LocationCodeNo
StockingFilterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.4/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 burden. It discloses only one behavioral nuance (StockingFilter affecting both Location and InventoryLocation) and says nothing about pagination defaults, result ordering, or whether the call is read-only and how much data it can return.

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?

Two short sentences with the resource definition front-loaded and the filter nuance second. Nothing is padded, though the second sentence uses an undefined internal term (InventoryLocation) without context.

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?

For an 11-parameter query tool with no annotations and no output schema, the definition is far too thin. An agent must guess at pagination behavior, filtering fields, and return shape before it can invoke this 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?

Schema description coverage is 0% across 11 parameters, yet the description only explains StockingFilter. Pagination, projection (fields, distinct, countOnly, totalCount), and LocationCode semantics are left entirely undocumented, so the description does not compensate for the schema gap.

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?

States the verb and resource ("Find Locations") and parenthetically scopes it to warehouse/inventory locations, which is more than a tautology. However, it never distinguishes this from the closely named siblings locations_get and inventory_locations_find, so an agent cannot confidently tell which tool returns what.

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?

No when-to-use or when-not-to-use guidance is given. Nothing indicates whether this is the general location lookup versus the inventory-specific variant, or when a get-by-key sibling would be preferable to a find.

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