Skip to main content
Glama

Search East End places

search_places
Read-onlyIdempotent

Searches the guide's verified venues across the Hamptons and North Fork: restaurants, breakfast, nightlife, wine, wellness, hair salons, ice cream, farm stands and oyster farms. The search covers the fields each section keeps, not only venue names: 'pick-your-own' matches the farms that run it, 'sunflowers' the ones that grow them, 'sorbet' the scoop shops that make it. Each match carries address, phone, an open/closed state with closing time computed on the East End's clock (America/New_York), and provenance: source and sourceUrl (what was read), lastVerified (when) and verifiedBy (manual = an editor read it, api = Google Places sweep). Where a venue publishes hours as prose rather than a machine schedule the row carries hoursText, the operator's published line, instead of openState. seasonalCaution appears on every venue verified as not year-round, 76 in all (16 of Montauk's restaurants, 12 of its bars). On those rows openState is computed only on a date inside a season window or a dated trading confirmation the guide holds and is otherwise omitted in every month, because the weekly hours an operator leaves published are the summer table. Where the operator has published a closure, openState reads "closed for the season" and seasonalCaution quotes the operator's words with the date they were read. Permanently closed venues are excluded. Returns up to 8 matches and the total matched. Each venue row also carries mapUrl, a link to the guide's live map centred on that venue (hamptonsverified.com/near-me?focus=…), and the answer carries one top-level mapUrl for the whole list. The map asks for the reader's location on their own device; the link carries no position. townScope reports how the place argument was read; townScope.recognized: false means the name matched no East End place, the rows array is empty, and didYouMean lists near matches where any exist.

Input Schema

NameRequiredDescriptionDefault
townNoA hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork', 'East End'), in the asker's own words: a trailing state and ZIP, British spellings and typos are resolved.
queryYesWhat to look for, e.g. 'rosé', 'lobster roll', 'sauna', 'sweet corn', 'pick-your-own'
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / town / description
      Previous value: -"A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork', 'East End'). Pass the asker's own words, trailing state and ZIP, British spellings and typos are resolved."New value: +"A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork', 'East End'), in the asker's own words: a trailing state and ZIP, British spellings and typos are resolved."
  2. Changed1 schema field changed
    • changedInput schema / properties / town / description
      Previous value: -"A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork', 'East End'). Pass the asker's own words — trailing state and ZIP, British spellings and typos are resolved."New value: +"A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork', 'East End'). Pass the asker's own words, trailing state and ZIP, British spellings and typos are resolved."
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "restaurant",
      -  "breakfast",
      -  "nightlife",
      -  "wine",
      -  "wellness",
      -  "ice-cream",
      -  "farm-stand",
      -  "oyster-farm"
      -]New value: +[
      +  "restaurant",
      +  "breakfast",
      +  "nightlife",
      +  "wine",
      +  "wellness",
      +  "salon",
      +  "ice-cream",
      +  "farm-stand",
      +  "oyster-farm"
      +]
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), yet the description still discloses genuinely non-obvious behavior: a hard cap of 8 matches plus a total, `openState` being omitted outside a season window on seasonal venues, `hoursText` substituting for `openState` when hours are prose, and `mapUrl` prompting for reader location with no position carried in the link. That is exactly the context annotations cannot supply.

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 first sentence is well front-loaded, but the body is a dense block mixing result-shape, provenance, seasonal logic and map behavior in long compound sentences. Details like '76 in all (16 of Montauk's restaurants, 12 of its bars)' are editorial color that does not help an agent decide or invoke.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-shape burden and does so: fields per row (address, phone, openState/hoursText, provenance, mapUrl), the top-level mapUrl, the 8-result cap plus total, and the empty-rows/didYouMean failure mode. Nothing an agent needs to interpret a response is missing.

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 67% (town and query documented, category enum undocumented but self-describing), and the description adds real meaning: the query matches section-specific fields such as pick-your-own, sunflowers and sorbet, not just names, and `townScope`/`didYouMean` explain how a failed place match is reported. Minor cost: it calls `town` 'the place argument', a naming mismatch that slightly obscures which parameter it describes.

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?

Opens with a specific verb ('Searches') and a scoped resource ('the guide's verified venues across the Hamptons and North Fork'), then enumerates the nine covered categories that map to the category enum. An agent can tell this apart from siblings like find_shops, things_to_do or whats_open_now without reading 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 Guidelines3/5

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

Usage is implied rather than stated: the category list and 'Permanently closed venues are excluded' indirectly route agents toward recently_closed or whats_open_now, but no sibling is named and no when-not condition is given. The description explains internal behavior (season windows, townScope) more than it explains tool selection.

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