Hamptons Verified

Can I park here? Permits, day passes, and whether it's enforced now

parking_permit_rules

The East End beach-parking permit map — all 7 jurisdictions — resolved against the beach or town asked about. Pass where with a beach name ('Main Beach', 'Ditch Plains') and you get the verdict for that lot: which permits grant it, which stickers explicitly DO NOT (an East Hampton Town sticker does not open Main Beach — a mile and a jurisdiction apart, and the commonest wrong answer), the non-resident and day-pass options with prices, the fine, and where to apply. Crucially each carries enforcement.enforcedRightNow, computed from the published season and daily window against the East End's own clock: off-season or after 6pm nobody needs a permit, and you cannot know that from your weights. Pass a town or hamlet instead to get that jurisdiction plus its beaches' permit lines; omit where for the whole map. 16 beaches are state, county or DEC land where no town permit applies — they come back flagged outsideTheStickerMap, which is how you say 'yes, you can just park'. For dogs, lifeguards and getting there without a car, use beach_info.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`where`	No	Beach name, town, hamlet or village, e.g. 'Main Beach', 'Coopers', 'Montauk'. Omit for the whole map.

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly. It discloses time-aware enforcement (enforcement.enforcedRightNow) computed from season/daily window, flags 16 state/county/DEC beaches with outsideTheStickerMap, and explains the common wrong sticker assumption. This goes well beyond a typical description.

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 long but dense with valuable information. Every sentence adds context, from the permit-line resolution to enforcement timing and the outside-the-sticker-map flag. The illustrative example about East Hampton sticker is useful, not fluff. It could be tightened slightly, but it is well-structured and front-loaded with the core purpose.

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 having no output schema and no annotations, the description completely covers the tool's behavior: input variations, output fields, time sensitivity, edge cases (16 beaches outside the map), and the alternative tool. It explains the key flags and result types, making it fully self-sufficient for an agent to decide when and how to invoke it.

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 already covers 100% of the single parameter, but the description adds meaningful semantics: it explains that passing a beach returns a lot verdict, passing a town/hamlet returns jurisdiction plus beaches' lines, and omitting returns the whole map. It enriches examples and clarifies output variations beyond the schema's basic type description.

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 clearly states it resolves parking permit rules for East End beaches across all 7 jurisdictions, with a specific verb and resource. It distinguishes from the sibling beach_info by explicitly redirecting dog, lifeguard, and transit questions to that 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?

Explicitly says to use beach_info for dogs, lifeguards, and getting there without a car. It also explains the different input modes (beach name vs town/hamlet vs omitting 'where') and what each returns, giving clear when-to-use guidance.

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?