Skip to main content
Glama

Data Candy: US business leads

List states and cities

list_locations
Read-onlyIdempotent

List US states with lead counts, or the cities of one state (pass state, optionally search to narrow by name). Use the exact values in the state and city filters. 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
limitNoMaximum cities to return (default 50).
stateNo2-letter state code: list the cities of this state.
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 behavior, so the safety profile is covered. The description adds genuinely new context: the operation is free (no credits consumed) and returned state/city identifiers must be reused verbatim. Return values are covered by the output schema.

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?

Two compact sentences plus a one-word cost note, with the primary listing mode front-loaded and the city-mode condition immediately after. No sentence is filler; even the terse 'Free.' carries decision-relevant information.

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?

For a three-parameter read-only listing tool with full schema coverage and an output schema, this covers mode selection, value constraints, and cost. The only minor gap is any note on how `limit` interacts with the state-level response, which the schema mostly handles.

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%, so the three parameters are already documented, establishing a baseline of 3. The description adds the meaningful 'use exact values' constraint and reiterates the state/search relationship, but says nothing about `limit` beyond what the schema states.

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 and resource — 'List US states with lead counts, or the cities of one state' — and makes the two operating modes unmistakable. It does not name or contrast itself with a sibling tool, which keeps it just short of a 5.

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 clearly explains how to select each mode: omit `state` for the state list, pass `state` for that state's cities, and optionally add `search`. It also gives the practical rule to reuse exact values from existing filters. It offers no explicit when-not guidance or named alternatives.

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