Skip to main content
Glama
Sign In
gobox-mcp

gobox-mcp

by Winter279
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_warehouses

Retrieve a list of warehouses with optional search by name and address details. Use pagination to control results.

Instructions

List all warehouses.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch by warehouse name
includeNoRelations: address
limitNoPage size
pageNoPage number

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description must bear the burden of transparency. It fails to mention pagination behavior, rate limits, or what 'all' means. The presence of optional search parameter 'q' contradicts 'list all'.

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?

The description is very short, which is concise, but it lacks important structure like a lead sentence summarizing functionality or formatting. It is minimally acceptable.

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?

Given the tool has 4 parameters and an output schema, the description is insufficiently complete. It does not explain that pagination, search, or relation includes are supported, leaving the agent to infer from schema alone.

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 each parameter having a description. The tool description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate.

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?

Description states 'List all warehouses' which is a specific verb and resource, but it oversimplifies by saying 'all' when input schema allows filtering and pagination. The sibling 'search_all_warehouses' exists, and no differentiation is provided, but the purpose is still clear.

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 usage guidelines provided. There is no guidance on when to use this tool versus alternatives like 'search_all_warehouses', and no context on prerequisites or use cases.

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