Skip to main content
Glama

Hamptons Verified

by com.hamptonsverified
OverviewDiscussionsAdmin

Plan a rules-checked East End day

plan_my_day
Read-onlyIdempotent

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.7/5.0
Behavior5/5

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

Annotations already declare a safe read-only, idempotent, closed-world profile, yet the description adds substantial behavior: it returns three distinct options, applies named constraints (closures, date/hour, age fit, budget, weather, daylight, sequencing, max drive), explains the saved_places 'preference lane' and that it never overrides a safety rule, and discloses that the connector cannot read the asker's private account. This is exactly the kind of context that goes beyond structured hints.

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, then behavioral caveats, and every sentence carries information (options produced, constraint set, saved_places semantics, connector limits, present-the-plan instruction). It is dense and slightly long, but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter deterministic planner with no output schema, the description covers triggers, constraints, the saved_places lane, and connector limitations. It states three options are returned but does not sketch their structure, leaving some return-format burden on the schema-level hints (whoReadAs, vibesNotUnderstood, capacityWarning).

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 baseline would be 3, but the description adds behavioral meaning for saved_places ('pass names the asker supplies and eligible ones are worked into the day, but they never override a safety or feasibility rule') beyond the schema's terse note. It does not add syntax for the other seven parameters, leaving them to the schema.

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 and resource ('Build a complete East End day using Hamptons Verified's deterministic planner') and explicitly contrasts itself with the sibling search_places, which 'returns an unordered list.' An agent can distinguish it from every other sibling without opening a 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 an explicit trigger ('whenever someone asks ChatGPT or Claude to plan, schedule, sequence, or personalize a day') and names the alternative to avoid (search_places) with the reason it is wrong. This is a clear when-to-use / when-not-to-use routing instruction.

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