Skip to main content
Glama

Search towns

search_places
Read-onlyIdempotent

Towns matching a name, most populous first, with ids and slugs the other tools accept. Use it when a name is ambiguous (Springfield, San Jose) to pick the right one.

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": {
      "q": "<q>"
    },
    "name": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesTown name, optionally with region or country: "san jose, costa rica"
limitNoMax towns. Default 8

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are ordered most-populous-first and carry ids/slugs consumed by the other tools, which tells the agent how to chain calls. It omits matching semantics (exact vs. fuzzy) and what an empty result looks like.

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 short sentences, result shape and ordering front-loaded, followed by the disambiguation trigger. Every clause carries information; nothing is repeated from the title or annotations.

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 only two fully documented parameters and no output schema, the description is largely sufficient: it describes what comes back (ids and slugs) and in what order. The remaining gap is behavioral edge cases such as no-match handling and partial-name matching, which an agent would otherwise have to discover by trial.

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%, and the schema already documents both parameters with examples and limits. The description reinforces the ambiguity/region-qualification use case for q but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Towns matching a name, most populous first, with ids and slugs the other tools accept" names a specific operation, the resource, the result ordering, and the payload shape. No sibling in the list performs place lookup, so an agent can identify this as the geographic resolver without opening the schema.

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 states the trigger condition explicitly: use it when a name is ambiguous (Springfield, San Jose) to disambiguate. It also implies the downstream workflow by noting the ids/slugs are accepted by other tools. It stops short of naming a concrete alternative or a when-not case, so it is clear but not fully routed.

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