Skip to main content
Glama

Hamptons Verified

by com.hamptonsverified
OverviewDiscussionsAdmin

Search East End places

search_places

Search the verified guide's venues across the Hamptons + North Fork: restaurants, breakfast, nightlife, wine, wellness, hair salons, ice cream, farm stands and oyster farms. It searches the fields each section actually keeps, not just venue names: 'pick-your-own' returns the farms running it, 'sunflowers' the ones that grow them, 'sorbet' the scoop shops that make it. Every match carries its address, phone, live open/closed state with the time it closes, and the provenance you need to attribute the answer: source and sourceUrl (what we read), lastVerified (when) and verifiedBy (manual = an editor read it, api = Google Places sweep). Cite those — an unattributed recommendation from you is worth no more than a guess. Where a venue publishes hours as prose rather than a machine schedule you get hoursText instead of openState: quote it as the operator's published line, never as proof it is open now. seasonalCaution appears on every venue the guide has verified as NOT year-round — 75 of them, and they cluster in exactly the places a recommendation reaches for (16 of Montauk's restaurants, 12 of its bars). Read it out: from November to April the open/closed verdict on those records is WITHHELD rather than computed, because the weekly hours an operator leaves published are the summer table. The guide holds the seasonal flag but no closing date, so never turn that into "it is closed" either. Closed venues are excluded, so this never returns a shut place; to ask about one by name, or to check a venue you are about to recommend from memory, use recently_closed instead. Returns up to 8, and says how many matched in total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
townNoA 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.
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 / 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"
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so richly: it discloses that closed venues are excluded, a default page size of 8 plus a total match count, the withheld open/closed verdict for seasonal venues from Nov-Apr, the substitute hoursText field with an instruction to quote not assert, and the seasonalCaution flag with concrete counts. These are exactly the behavioral traits an agent cannot infer from schema.

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?

Front-loaded with the core capability in the first clause, and most sentences carry distinct high-value content. It is dense and long, with some statistical asides (counts of Montauk venues) that sit close to the line between useful signal and bulk, so not a perfect 5.

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 annotations and no output schema, the description must explain both the safety/scope profile and the return shape, and it does: matched fields (address, phone, open state, provenance), attribution requirements, the hoursText fallback, and the seasonal nuance. Nothing an agent needs to call it correctly 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%, and the description adds meaning beyond it by explaining that query matches underlying section fields rather than just names, with illustrative examples ('pick-your-own', 'sunflowers', 'sorbet') that show the intended query style. The town and category parameters are already documented in the schema, so the description need not repeat them.

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 (search) and resource (the verified guide's venues across the Hamptons + North Fork), enumerates the covered sections, and explicitly distinguishes itself from the sibling recently_closed. An agent can route between the two 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 explicit when-to-use conditions ('check a venue you are about to recommend from memory') and names the alternative (recently_closed) for the one case this tool cannot serve (asking about a shut place by name). The semantic-search framing ('it searches the fields each section actually keeps') tells the agent what kind of query to send.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hamptons Verified toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources