Skip to main content
Glama

Hamptons Verified

by com.hamptonsverified

Beach: dog rules today, parking permit, lifeguards

beach_info

One named beach (or every verified beach in a town or hamlet — 'Amagansett, NY' and 'Sag Harbour' resolve, and readAs reports which place was answered for) with the answers people actually arrive with: whether dogs are allowed TODAY, what parking permit the lot needs, whether you can get there without a car, lifeguard hours and rip-current notes. 49 beaches on both forks, each with its governing town/village/state source and the date we last read it. Call this for any dog question — the rule is per-month and splits morning from daytime, so most South Fork ocean beaches are off-leash at dawn and closed to dogs in daylight from May to September, and no model can know today's answer. Also call it before saying anyone can just park at a beach. For the full permit map across all 7 jurisdictions and non-resident day passes, use parking_permit_rules instead. Returns up to 5.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
beachYesBeach name, town, hamlet or village, e.g. 'Georgica', 'Main Beach' or 'Amagansett'

TDQS

A4.6/5.0
Behavior4/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 well: it discloses that town/hamlet queries return multiple beaches, that readAs reports the resolved place, that results include source and date, and that output is capped at 5. It doesn't cover every edge case, but the main behavioral traits are clearly conveyed.

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 fairly long but dense with necessary detail. It is front-loaded with the main purpose, then adds resolution behavior, usage guidance, and a sibling alternative. Every sentence contributes, though some tightening could make it even more scannable.

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?

Given the simple single-parameter schema and lack of annotations or output schema, the description is remarkably complete: it covers what results are returned, the dynamic dog-rule aspect, the parking permit scope, source/date metadata, output limit, and when to use an alternative. The agent has enough to invoke the tool correctly in context.

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?

The schema covers the parameter name and example inputs, but the description adds meaning beyond that by explaining how town/hamlet names resolve, that readAs reports the matched place, and that multiple results (up to 5) are possible. This is useful context the schema alone does not provide.

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 that the tool returns beach-specific information (dog rules today, parking permit, car-free access, lifeguards, rip currents) for one named beach or all verified beaches in a town. It explicitly distinguishes itself from sibling tools by naming parking_permit_rules as the alternative for permit maps.

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?

It gives direct invocation guidance: 'Call this for any dog question' and 'Also call it before saying anyone can just park at a beach.' It also states when to use parking_permit_rules instead, providing a clear exclusion and alternative.

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
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