Skip to main content
Glama

Hamptons Verified

by com.hamptonsverified
OverviewDiscussionsAdmin

Plan a rules-checked East End day

plan_my_day

Build a complete East End day using Hamptons Verified's deterministic planner. Use this whenever someone asks ChatGPT or Claude to plan, schedule, sequence, or personalize a day—not search_places, which returns an unordered list. The tool produces three distinct options and applies the same constraints as the website before returning anything: permanent closures, the selected date and opening hour, age fit, budget, weather, daylight, geographic sequencing and the maximum drive between consecutive stops. saved_places is a preference lane: pass names the asker supplies and eligible ones are worked into the day, but they never override a safety or feasibility rule; the rest of the stops remain discoveries. This connector cannot read the asker's private Hamptons Verified account, browser or saved list, so ask for the names when they want them included. Present the returned plan; never replace a stop from your own memory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whoNoWho the day is for: solo, couple, family, friends, first-date, in-laws. There is no 'group' value — a group of friends is `friends` and a group with children is `family`; pass either and the answer reports which was used in `whoReadAs`. For the size of the group use `party_size`, which is a different question.
dateNoISO date in East End local time; defaults to today.
seedNoOptional stable seed when the asker wants the same result repeated.
townNoA hamlet or region to keep the day around. Omit for the full East End.
vibesNoComma-separated interests. The planner understands exactly these: quiet, active, foodie, cultural, beach, adventure, romantic, off-season, shopping, anything. Anything else is reported back in `vibesNotUnderstood` rather than acted on — it is never silently dropped.
budgetNo
energyNo
party_sizeNoHow many people are coming, as a number. Stops whose operator publishes a maximum BELOW it come back with a `capacityWarning` quoting that operator's own line — several Sag Harbor charters cap at six. Omit when the asker did not say; nothing is guessed.
saved_placesNoComma-separated saved venue names supplied by the asker. Never infer private account data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / party_size
      Added value: +{
+  "description": "How many people are coming, as a number. Stops whose operator publishes a maximum BELOW it come back with a `capacityWarning` quoting that operator's own line — several Sag Harbor charters cap at six. Omit when the asker did not say; nothing is guessed.",
+  "type": "string"
+}
    • changedInput schema / properties / vibes / description
      Previous value: -"Comma-separated interests such as quiet, foodie, cultural, beach, adventure, romantic, active, or off-season."New value: +"Comma-separated interests. The planner understands exactly these: quiet, active, foodie, cultural, beach, adventure, romantic, off-season, shopping, anything. Anything else is reported back in `vibesNotUnderstood` rather than acted on — it is never silently dropped."
    • addedInput schema / properties / who / description
      Added value: +"Who the day is for: solo, couple, family, friends, first-date, in-laws. There is no 'group' value — a group of friends is `friends` and a group with children is `family`; pass either and the answer reports which was used in `whoReadAs`. For the size of the group use `party_size`, which is a different question."
    • removedInput schema / properties / who / enum
      Removed value: -[
-  "solo",
-  "couple",
-  "family",
-  "friends",
-  "first-date",
-  "in-laws"
-]
  2. Added

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 of behavioral disclosure, and it does so thoroughly: it discloses determinism, that three options are produced, the full constraint set applied before returning (closures, date/opening hour, age, budget, weather, daylight, geographic sequencing, max drive), that saved_places is a preference lane that never overrides safety rules, and that the connector cannot read private account data. This is rich behavioral context beyond any structured field.

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 (~200 words) but dense — every sentence carries operational meaning and there is no fluff. The usage-vs-alternative guidance is front-loaded in the first sentence, and later sentences each add a distinct behavioral fact. For a 9-parameter planner, the length is justified; a minor trim of the saved_places sentence could tighten it, but it is not bloated.

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 and no annotations, the description must carry the full contract, and it does: it pre-announces return shape (three distinct options), reports fields (whoReadAs, vibesNotUnderstood, capacityWarning), covers privacy limitations, and states the deterministic constraint set. For a complex 9-param tool with zero structural safety nets, nothing an agent needs to call it correctly 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 78%, so the schema already documents most parameters; the description adds genuine value on top for key ones: saved_places is explained as a preference lane that never overrides rules, party_size gains the capacityWarning behavior with a concrete Sag Harbor example, and vibes gains the vibesNotUnderstood non-silent-drop behavior. A few params (town, energy, budget) rely on the schema alone, but the description compensates where behavior matters most.

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?

States a specific verb (build/plan), a concrete resource (a complete East End day), and immediately distinguishes itself from the sibling search_places ('which returns an unordered list'). The title reinforces scope. An agent can tell exactly what this tool produces and how it differs from nearby tools 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?

Explicitly names the trigger condition ('whenever someone asks... to plan, schedule, sequence, or personalize a day') and names the alternative it is not (search_places). It also gives operational guidance for saved_places — ask the user for names when they want them included — and instructs the agent to present rather than substitute stops. Nothing is left to inference.

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