Skip to main content
Glama

Search places

search_places
Read-onlyIdempotent

Search verified places in the Finger Lakes and Southern Tier of New York (restaurants, bars, wineries, breweries, shops, lodging, parks, trails, services, civic offices). Each result has source_url, verified_date, hours with their verification status, open_now, and a call_to_confirm flag. Unknown hours are never treated as open.

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

Input Schema

NameRequiredDescriptionDefault
townNoTown or county, e.g. "Hornell", "Watkins Glen", "Steuben County"
limitNo
queryNoName or words, e.g. "pizza", "Sixty Six", "waterfall"
offsetNo
categoryNoType or category: restaurant, eat_drink, bar, winery, brewery, cidery, distillery, lodging, shopping, park, trail, museum, attraction, service, health, civic, church, or a category word such as "pizza" or "bakery"
open_nowNoOnly places whose posted hours show them open right now (America/New_York)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the verification metadata returned per result (source_url, verified_date, hours verification status, call_to_confirm) and the crucial rule that "Unknown hours are never treated as open" — a semantic gotcha for open_now that no annotation conveys. It omits pagination behavior and result ordering, which keeps it from a 5.

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?

Three sentences, front-loaded with the verb, resource, and scope, then return shape, then the open_now rule. The category parenthetical is long but earns its place by defining coverage boundaries; nothing is redundant.

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?

There is no output schema, and the description compensates well by listing the returned fields and the call_to_confirm signal. With 6 optional parameters at 67% coverage, the remaining gap is pagination/result-cap behavior, which the description does not address.

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 67%, so most parameters (town, query, category, open_now) are already documented in the schema. The description adds meaning for open_now only, by stating the unknown-hours rule; limit, offset, and pagination semantics are left entirely to the schema, and no example query syntax is offered beyond what the schema provides.

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?

States a specific verb and resource ("Search verified places") plus a precise geographic scope (Finger Lakes / Southern Tier of New York) and an enumerated set of covered categories, which lets an agent tell it apart from a single-record lookup like get_place or a narrow filter like open_now. It stops short of naming any sibling or stating how it differs from them, so the differentiation is inferred rather than declared.

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 by the category list and the open_now qualifier, so an agent can guess this is the discovery tool for the region. There is no explicit when-to-use/when-not-to-use guidance and no statement about which sibling to prefer for a known-venue lookup or a beverages-only search.

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