Skip to main content
Glama
Sign In

Hamptons Verified

by com.hamptonsverified
OverviewDiscussionsAdmin

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

picnic_spots
Read-onlyIdempotent

Verified East End picnic grounds, 25 in all: public parks, state and county parks, preserves, beach-grass strips, winery lawns and historic gardens, each with the rules set by whoever owns the ground (New York State, Suffolk County, a town, a village, a winery). alcohol is a sentence per spot, not a boolean: wine-only is a winery lawn where only the estate's wine is permitted, and allowed-with-permit means a permit from permitUrl is required first. 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). Where only hoursText comes back the published line was not machine-readable and is given as published. allows filters to spots that permit it. The guide holds no drinking rule for the ocean beaches, so none is returned for them. Returns up to 8. 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'), in the asker's own words.
queryNoWhat to look for, e.g. 'sunset', 'shade', 'oceanfront', 'quiet', 'big group', or a park's name.
allowsNoFilter to spots that permit this. 'alcohol' includes wine-only and permit-only spots, each flagged in its own `alcohol` line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"What they want, e.g. 'sunset', 'shade', 'oceanfront', 'quiet', 'big group', or a park's name."New value: +"What to look for, e.g. 'sunset', 'shade', 'oceanfront', 'quiet', 'big group', or a park's name."
    • changedInput schema / properties / town / description
      Previous value: -"A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words."New value: +"A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'), in the asker's own words."
  2. 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"
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses many behavioral traits: alcohol is a sentence not a boolean, wine-only and allowed-with-permit have specific meanings, glassBottles prohibitions hold even where alcohol is allowed, closesAt is computed from coordinates for today, hoursText is used when sunrise/sunset text is not machine-readable, results cap at 8, and townScope.recognized false empties rows and returns didYouMean. These are substantial additions beyond the read-only/idempotent annotations.

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 dense but front-loads the core purpose and scope, then layers in nuanced field semantics. Most sentences carry useful information, though the length and number of details make it heavier than typical tool descriptions.

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?

There is no output schema, so the description must explain return behavior—and it does: result limit, how closesAt and hoursText are resolved, townScope reporting, empty rows with didYouMean, and the omission of drinking rules for ocean beaches. This is complete enough for an agent to call and interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents town, query and allows. The description reinforces how the town argument is read and clarifies that allows filtering includes wine-only and permit-only alcohol spots, but most of that is already stated in the schema's allows description. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource: verified East End picnic grounds, 25 in all, including public parks, preserves, beaches, winery lawns and historic gardens. It specifies the key attributes (alcohol, glass bottles, grills, dogs, hours) but does not explicitly contrast itself with sibling tools like beach_info or things_to_do.

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 through the filter parameter and the explanation of townScope and the ocean-beach exclusion, but there is no explicit when-to-use or when-not-to-use guidance versus alternatives. An agent can infer this is for picnic-rule lookup, yet the description never names a sibling tool or a decision rule.

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