Skip to main content
Glama

list_locations

Read-onlyIdempotent

Retrieves warehouse named locations and zones, including docks, shelves with items, delivery stations, keep-out areas, and speed limits.

Instructions

Named locations (docks, shelves with their items, stations with what was delivered) and zones (keep-out areas, speed limits).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description still adds useful payload context beyond them, revealing that entries are not bare names but carry inventory detail (items on shelves, deliveries at stations) and that zones include constraints like keep-out areas and speed limits. It omits any statement about ordering, pagination, or how large the response is.

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 tight sentence with every clause earning its place, and the two data families (locations, zones) are front-loaded. The tradeoff is that it reads as a fragment with no verb, which slightly weakens it as a standalone instruction.

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 zero-argument read-only lister with no output schema, the description does the minimum needed to say what comes back, and annotations cover safety. However, with no output schema the description is the only guide to response shape, and it only sketches content categories without indicating structure, nesting, or size.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is nothing the description could clarify about arguments. The description correctly implies an unfiltered full listing with no arguments.

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 is a noun phrase rather than a verb+resource statement, but the parenthetical examples (docks, shelves with items, stations with deliveries, keep-out zones, speed limits) make the returned resource set concrete and distinguishable from list_robots or get_params by content alone. It stops short of stating the action explicitly and never differentiates itself from siblings in words.

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 alternatives such as get_robot_state or plan_route, and no stated preconditions. The reader must infer that this is the discovery call before navigate_to or plan_route, which is left entirely implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.