Skip to main content
Glama

Get a place

get_place
Read-onlyIdempotent

Read one place from Google Places by its id, in the shape a wording's place takes in create_poll and update_poll: its name, kind (country, region, county, city or postal_code) and ISO country and region codes. Any other place, such as an address or a business, is refused. Models never see a wording's place; it is there so results can be shown by place. (GET /api/v1/places/{id})

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": {
      "id": "<id>"
    },
    "name": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA Google place id, from search_places.
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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, openWorldHint=false and non-destructive, so the safety profile is covered. The description adds genuine behavior beyond that: which place kinds succeed, that other kinds are refused (an error path), the returned fields, and the underlying endpoint. It does not cover billing/rate behavior, which instead lives in the session parameter.

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

Conciseness3/5

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

The core read/what-is-returned statement is front-loaded and useful, but the clause "in the shape a wording's place takes in create_poll and update_poll" is convoluted and leans on undefined jargon ("wording"), and the aside about models never seeing a wording's place is tangential to invoking the tool.

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, no output schema, and annotations covering safety, the description is nearly self-sufficient: it names the returned fields, the refusal case, and the endpoint. The main residual gap is that the "wording" concept is never defined, which could confuse an agent reasoning about what it is fetching.

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 both id and session are fully documented in the schema, including the id's source (search_places) and the session's billing purpose. The description adds no syntax or format detail beyond that, so the baseline of 3 applies.

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 ("Read one place from Google Places by its id") and immediately bounds the scope: only wording-shaped places (name, kind, ISO codes), with addresses and businesses explicitly refused. An agent can tell this is a single-record lookup distinct from a search.

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?

Explains the intended context — retrieving the place that create_poll and update_poll store so results can be displayed by place — and gives a clear exclusion (addresses/businesses are refused). It stops short of explicitly routing the agent to search_places for the id, though the schema's id description supplies that link.

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.