Skip to main content
Glama

Get one place

get_place
Read-onlyIdempotent

One verified place by id, slug or name (fuzzy name matching, aliases and former names included), with hours, open_now, source_url, verified_date, call_to_confirm and the owner claim link. Returns found=false rather than guessing.

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": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
nameNoe.g. "Sixty Six on Broadway"
slugNo
townNoTown or county, e.g. "Hornell", "Watkins Glen", "Steuben County"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, so the safety profile is covered. The description adds genuinely new behavior: fuzzy name matching, alias/former-name resolution, and a found=false fallback instead of guessing — the last being important for how an agent should interpret a miss.

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 tight clauses: the retrieval target and return contents first, then the failure mode. No filler, and the most decision-relevant fact (found=false instead of guessing) is placed last for emphasis.

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?

No output schema exists, so listing the returned fields is necessary and done well. For a 4-param, zero-required lookup tool this is nearly complete; the missing piece is guidance on which identifier to prefer and whether town narrows or filters the lookup.

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?

With 50% schema description coverage the description should compensate more than it does. It clarifies that name matching is fuzzy and alias-aware, but never mentions the town parameter or explains how the four optional parameters combine or which takes precedence when several are supplied.

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 ('One verified place by id, slug or name') and enumerates the returned fields (hours, open_now, source_url, verified_date, call_to_confirm, claim link), which sets it apart from a general search tool. It never names the sibling search_places explicitly, so the differentiation from list-style retrieval is left implicit.

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?

Usage is implied rather than stated: an agent can infer it should call this when it already has an identifier (id, slug, name). There is no explicit when-not guidance or pointer to an alternative such as search_places for exploratory lookups, which is the main gap.

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