Skip to main content
Glama

1Network local business directory (read-only)

List states and cities

list_locations
Read-onlyIdempotent

List US states with business counts, or the cities of one state (pass state, optionally search to narrow by name). Free.

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
limitNoHow many cities (default 25).
stateNo2-letter state code: list the cities of this state. Leave out to list the states.
searchNoOnly cities whose name contains this text.

Output Schema

NameRequiredDescriptionDefault
levelYes
citiesYes
statesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description adds real context beyond them: state results include business counts, and the call is 'Free', which matters for cost-aware planning. It does not discuss pagination or limits for the city list.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the two-mode behavior, the mode-selecting parameter and the cost note all land in one pass.

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

Completeness4/5

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

With an output schema present, return values need not be explained, and the description still previews that states come with business counts. What remains thin is the city-list side, where `limit` defaults and any truncation behavior go unmentioned.

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 coverage is 100%, so all three parameters are already documented, and the description mainly restates `state` and `search` behavior. The `limit` parameter (default 25 cities) is never mentioned, so the description adds only marginal meaning over the schema.

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 uses a concrete verb+resource ('List US states', 'cities of one state') and spells out both operating modes, so an agent can tell it apart from count_businesses or search_businesses by output shape. It stops short of naming any sibling explicitly, so it is clear but not maximally differentiated.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit conditional guidance: pass `state` to get cities, leave it out to get states, and add `search` to narrow cities by name. What is missing is any statement of when not to use it or which sibling to prefer for counting/searching businesses.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources