Skip to main content
Glama

Things to do: what's in season, and who actually runs it

things_to_do

What there is to DO on the East End — activities (surfing, kayaking, paddleboard, hiking, mountain biking, camping, horseback, climbing, shellfishing, birding, skydiving), on-water businesses (fishing charters, marinas, sailing schools, yacht clubs, jet-ski rental) and wildlife you can go and see (seals, whales, ospreys, sea turtles, sharks). Call this for any what-should-we-do, where-can-I-, outdoors, on-the-water, boating, hiking or wildlife question. Two things make it worth the call over answering from memory. First, SEASON: every result carries inSeasonNow, computed against the East End's own calendar month, so 'can we go whale watching' gets a real yes or no with the window, and a seasonal activity is never recommended into the wrong month — pass month to plan ahead. Second, and more important, noCommercialOperator: true — the guide's checked finding that NOBODY here teaches or rents this. There is no kitesurfing school at Napeague and no climbing guide at Shadmoor; those are exactly the answers a model gives fluently and wrongly, and this is the field that contradicts them. Where operators DO exist they come with phone, booking page, published price and their own source and date — never invent one. Also returns the permits an activity is unlawful without (shellfishing needs two), the conditions it needs, minimum-approach rules for wildlife, and skill and age limits. seasonUnknown counts records whose operator publishes only 'Summer-only' with no dates: quote that verbatim, do not turn it into a claim they are open. With neither query nor town nothing is looked up — you get the kinds and towns covered, so ask. Returns up to 8.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
townNoA hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words.
monthNoMonth to judge the season for, e.g. 'October' or 'Oct'. Omit for now — the default is today's month on the East End.
queryNoWhat they want to do, e.g. 'kayak', 'fishing charter', 'surf lesson', 'seals', 'hiking', 'camping', 'whale watching', or an operator's name.

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: every result carries `inSeasonNow`, `noCommercialOperator: true` means no operator exists, operators are never invented, `seasonUnknown` must be quoted verbatim, and results are capped at 8. This is a rich, honest disclosure of how the tool behaves beyond just 'what it does.'

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, but every sentence adds value—scope, usage, key features, special flags, and limits. It is front-loaded with the main purpose and structured logically. Slightly verbose, but the density of critical information justifies the length.

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?

For a tool with no output schema and no annotations, the description is remarkably complete. It covers what is returned, seasonality logic, the no-commercial-operator edge case, permits, conditions, skill limits, and the empty-query response. Agents have enough context to invoke it correctly.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds substantial meaning beyond the schema. It explains month defaults to current, gives query examples, and specifies that passing neither query nor town returns kinds and towns instead of looking up. This contextual information helps the agent use parameters correctly.

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 what the tool does: 'What there is to DO on the East End' and enumerates activities, businesses, and wildlife. It explicitly directs agents to 'Call this for any what-should-we-do, where-can-I-<verb>, outdoors, on-the-water, boating, hiking or wildlife question,' distinguishing it from siblings like beach_info or play_sport.

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?

Provides explicit when-to-use guidance: 'Call this for any what-should-we-do...' and explains the fallback when no query or town is given. It also differentiates from answering from memory by highlighting the tool's specialized seasonality and no-commercial-operator verification, giving clear context for preference over alternative approaches.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

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