Skip to main content
Glama

Hamptons Verified

by com.hamptonsverified
OverviewDiscussionsAdmin

What is on: tonight, this weekend, next Saturday

upcoming_events
Read-onlyIdempotent

Source-verified East End events, each with its official sourceUrl and the date we last checked it. Call this for anything time-bound — tonight, this weekend, next Saturday, 'what's on in Montauk' — and never answer those from memory: a model cannot know a 2026 concert series. Dates and times are East End local (America/New_York), so 'tonight' is today's date here even if your own clock has rolled over. Read access before you recommend anything: it is the organiser's own gate — sold-out (nothing left to buy), approval or invite-only (registering is a request the host may refuse), members-only (club members only), waitlist, or open — and a gated room presented as bookable sends someone to a door they are not on the list for. Quote accessNote as written; an absent access means the record states nothing, which is not the same as open. Pass town to ask about one place; the answer tells you the total matching, whether it was truncated, and — when nothing matches — the next event there instead, which is how you say 'nothing tonight in Montauk' without guessing. townScope.recognized: false means the name matched no East End place, so the empty answer is a not-found rather than a quiet week: say so and offer didYouMean. Defaults to the next 7 days; returns up to 12.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoISO date, default from+7. Same date as `from` for a single day/tonight.
whoNoWho is going. Omit for a general visitor: programs the venue itself describes as for kids or teens only (storytime, 'grades 4-9', 'ages 2-5') are left out and counted in `leftOutForKidsOrTeens`; family events stay in. Pass `kids`, `teens` or `family` when the asker mentions children, teens or family, and `everyone` to get the whole calendar.
fromNoISO date, default today (East End local)
townNoA hamlet ('Montauk') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / who
      Added value: +{
+  "description": "Who is going. Omit for a general visitor: programs the venue itself describes as for kids or teens only (storytime, 'grades 4-9', 'ages 2-5') are left out and counted in `leftOutForKidsOrTeens`; family events stay in. Pass `kids`, `teens` or `family` when the asker mentions children, teens or family, and `everyone` to get the whole calendar.",
+  "enum": [
+    "kids",
+    "teens",
+    "family",
+    "everyone"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-open-world), yet the description adds substantial behavioral context beyond them: the full `access` gate taxonomy and why presenting a gated room as bookable is harmful, the timezone caveat that 'tonight' is East End local even if the caller's clock rolled over, the meaning of an absent `access` versus `open`, the 12-result cap, and the truncation/next-event fallback. This is exactly the value-add the dimension is looking for.

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 purpose, then usage triggers, then output-handling, so the most important material comes first. It is a dense paragraph rather than a list, and a few clauses (e.g. the full re-explanation of `accessNote`) could be tightened, but nearly every sentence carries operational content.

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 output schema, the description carries the full burden of explaining returns and does so: total matching, truncation flag, next-event fallback, `townScope.recognized`/`didYouMean`, `access`/`accessNote`, and the default window and result cap. Nothing an agent needs to interpret or act on the response 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 already 100%, so baseline is 3, but the description adds real meaning: 'Pass `town` to ask about one place' plus the hamlet-vs-region distinction and 'pass the asker's own words', and how the response reveals `townScope.recognized: false` as a not-found rather than a quiet week. It reinforces the `who` selection rule for kids/teens/family asks. It slightly undersells the `to`/`from` pairing beyond what the schema says, so not a 5.

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?

Opens with a specific resource and its distinguishing attributes: source-verified East End events, each carrying an official sourceUrl and a last-checked date. The scope ('anything time-bound') is sharp enough to separate it from evergreen siblings like things_to_do, though it never names a sibling explicitly. An agent knows exactly what it gets without opening the 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 concrete invocation triggers ('tonight, this weekend, next Saturday, what's on in Montauk'), an explicit prohibition ('never answer those from memory: a model cannot know a 2026 concert series'), and a pre-recommendation prerequisite ('Read `access` before you recommend anything'). It also prescribes downstream behavior for truncation and empty results, which is unusually actionable 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 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