Skip to main content
Glama

Search places

search_places
Read-onlyIdempotent

Up to five places from Google Places whose names match q: countries, states and provinces, counties, cities and ZIP or postal codes, never an address or a business. Each has an id and its text; read the one you want with get_place, and put the result in the wording's place. (GET /api/v1/places)

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
qYesWhat to look for, such as Alaska or Bethel.
sessionNoOptional: one UUID you make for a search and the read that follows it, which Google bills as one session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description's job is to add context — and it does: result cap of five, the per-result shape (an id and its text), and even the underlying endpoint. It says nothing about ranking, partial matches, or empty results, which are the remaining behavioral unknowns for a search.

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?

Densely packed but front-loaded: count, source, and match semantics come first, follow-up tooling second. The colon-separated enumeration and the trailing '(GET /api/v1/places)' make it slightly run-on, and the endpoint parenthetical is of marginal use to an agent.

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 parameters, full schema coverage, annotations, and no output schema, the description supplies what the structured fields cannot: result cardinality and the shape of each returned item. Missing only edge-case behavior (no matches, ambiguous names), which is minor for this tool class.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning to 'q': it enumerates accepted entity types (countries, states/provinces, counties, cities, ZIP/postal codes) and states the negative constraint that the schema only hints at. The session parameter is left entirely to the schema, which is acceptable given its detailed description.

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?

States a specific verb and resource (search Google Places for name matches) plus precise scope: up to five results, geographic entity types only, 'never an address or a business'. It also routes the agent to get_place, so it is distinguishable from that sibling without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-not ('never an address or a business'), an explicit follow-up path ('read the one you want with get_place'), and the intended use ('put the result in the wording's place'). The selection condition between search and read is unambiguous.

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.