Skip to main content
Glama

Search places

search_places
Read-onlyIdempotent

Find ZIP codes by ZIP, city or county name, nationwide unless a state is given.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesZIP, city or county name
stateNotwo-letter state code to search within

Output Schema

NameRequiredDescriptionDefault
placesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the geographic-scope behavior ('nationwide unless a state is given'); it says nothing about result caps, matching behavior, or ambiguity handling, which are the traits an agent would actually want here.

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 the action, the inputs, and the scope constraint. No filler or redundancy.

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?

This is a simple two-parameter read tool with full schema coverage, annotations covering safety, and an output schema so return values need no explanation. The only meaningful gap is the absence of routing guidance versus sibling lookup tools.

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 both parameters are already documented, and the baseline is 3. The description restates the query forms and clarifies that state narrows the search rather than expanding it, but adds no syntax, format, or matching details beyond 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 states a specific verb and output ('Find ZIP codes') plus the accepted input forms ('by ZIP, city or county name'), which is enough for an agent to identify it as a lookup/search tool. It doesn't name or contrast with siblings like geocode_address or get_place, so it falls 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 Guidelines3/5

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

'nationwide unless a state is given' gives a scoping condition for the search, which implies when to pass state. However, there is no explicit guidance on when to choose this over geocode_address or get_place, and no stated limits or exclusions.

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