Hamptons Verified

Picnics: where alcohol, a grill and the dog are actually legal

picnic_spots

Verified East End picnic grounds — public parks, state and county parks, preserves, beach-grass strips, winery lawns and historic gardens — with the rule that decides whether the plan is legal. Call this for any picnic, blanket, park, park-hours, barbecue or fire-pit question, and ALWAYS before saying anyone can drink outdoors: the alcohol rule is set by whoever owns the grass (New York State, Suffolk County, a town, a village, a winery) and splits roughly a third prohibited, a third bring-your-own, a third wine-only-or-permit-only. Answering that from memory is the classic confident wrong answer, and it costs the asker a village summons rather than a bad meal. alcohol is a sentence to quote, not a boolean: wine-only is a winery lawn where the estate's wine is fine and your bottle is not, and allowed-with-permit means not allowed until the permit in permitUrl is in hand. glassBottles: prohibited holds even where alcohol is allowed. fireOrGrill and dogs are per-spot. 15 of these publish hours as "Sunrise to sunset" or "Dawn to dusk", so closesAt is resolved from THAT spot's own coordinates for today — "8:09 PM (sunset)" is tonight's sunset there, which is not something you can know. Where only hoursText comes back the published line was not machine-readable: quote it, do not turn it into a claim about right now. Pass allows to filter to what the picnic needs. The guide holds NO drinking rule for the ocean beaches — those are beach_info's, which carries dogs and permits but not alcohol — so never infer one from these. Returns up to 8.

Input Schema

TableJSON Schema

Name	Required	Description
`town`	No	A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words.
`query`	No	What they want, e.g. 'sunset', 'shade', 'oceanfront', 'quiet', 'big group', or a park's name.
`allows`	No	Filter to spots that permit this. 'alcohol' includes wine-only and permit-only spots, each flagged in its own `alcohol` line.

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and exceeds it. It discloses nuanced behaviors: the alcohol field is a sentence not a boolean, closesAt is computed from each spot's coordinates for today's sunset, hoursText should be quoted when not machine-readable, and results are capped at 8. It also alerts the agent to the legal stakes of guessing, which is critical context.

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?

The description is a dense paragraph, but every sentence carries substantive information—purpose, usage, alcohol rule details, time resolution logic, and exclusions. It is front-loaded with purpose and usage, though the lack of formatting (bullets or sections) makes it less scannable. Slightly verbose for a tool definition, but no word is wasted.

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?

Despite no output schema, the description provides a thorough mental model of the response: it mentions fields like `alcohol`, `glassBottles`, `fireOrGrill`, `dogs`, `closesAt`, `hoursText`, and `permitUrl`, and explains how to interpret them. It also covers edge cases (sunset-based closing times, non-machine-readable hours) and explicitly distinguishes from beach_info, making it complete for the tool's complexity.

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 100%, so the baseline is 3. The description adds value beyond the schema by explaining the `allows` filter behavior: 'Pass `allows` to filter to what the picnic needs' and clarifies that 'alcohol' includes wine-only and permit-only spots, each flagged in its own alcohol line. This semantic nuance improves the agent's ability to use the filter correctly.

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?

The description explicitly defines the tool as 'Verified East End picnic grounds' with a clear scope (public parks, state and county parks, winery lawns, etc.) and a specific purpose: determining the legality of a picnic plan (alcohol, grill, dogs). It distinguishes itself from sibling tools by stating the ocean beaches are covered by 'beach_info's', not this tool.

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?

The description gives explicit when-to-use guidance: 'Call this for any picnic, blanket, park, park-hours, barbecue or fire-pit question, and ALWAYS before saying anyone can drink outdoors.' It also provides a when-not-to-use exclusion: 'The guide holds NO drinking rule for the ocean beaches — those are beach_info's' and warns against relying on memory, making the usage conditions unmistakable.

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

All Hamptons Verified tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

Most tools target a distinct domain, and the descriptions explicitly cross-reference each other (e.g., beach_info vs parking_permit_rules). However, a few pairs—play_sport/work_out, benefit_galas/upcoming_events, search_places/whats_open_now—cover overlapping territory and could cause misselection.

Naming Consistency2/5

Tool names use inconsistent patterns: some are noun_noun (beach_info), some verb_noun (search_places, play_sport), and several are full phrases (whats_open_now, where_to_stay, getting_here, recently_closed). This makes the naming unpredictable despite consistent snake_case.

Tool Count4/5

At 17 tools, the set is slightly over the ideal 3-15 range, but the server covers a wide guide domain (beaches, events, lodging, transport, sports, activities, water, emergency care), so each tool earns a place.

Completeness4/5

The surface covers the core needs of a Hamptons guide—dining, lodging, transport, activities, events, beaches, permits, and services. Minor gaps exist (e.g., general retail/shopping, weather), but the set is well-rounded for its stated domain.

Resources

Need Help?