Skip to main content
Glama

Getting here: fares, ferries, and whether the road is moving

getting_here

How to get to the East End and around it: Hampton Jitney, the LIRR Cannonball and off-peak Montauk Branch, Blade, seaplanes, the three ferries, cycling, the ride-hail reality, and driving — each with the operator's published fare, season and stop list, plus when the guide last read it. Call this for any getting-there, how-long, how-much or when-should-I-leave question, and for 'without a car'. Two things here are unknowable from your weights and worth the call on their own: current fares (a prepaid Jitney seat is a different number from one paid on board, and Cross Sound adds a fuel surcharge to every published fare), and roadConditionsNow — whether this instant falls inside one of the published NY-27 crawl windows, computed against the East End's own clock (America/New_York), with the next window's start time so you can tell someone when to leave instead of guessing, and all three published windows with their days and hours so a departure time that is not now still gets a real answer. Pass to with the asker's own destination words: the answer then reports which Jitney stops actually serve it and the drive-time row for that run, with the guide's typical AND summer minutes rather than one averaged number. Pass mode: 'car-free' for someone without a car. Every figure carries its source; where sourceCaveat appears, the record is filed against a link that does not publish it — attribute it to the guide and do not cite that URL. There is no live incident feed behind this: it is the published pattern, not what the road is doing this minute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoWhere they are going — a hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words. Omit for the whole picture.
modeNo'car-free' when the asker has no car (drops driving); 'driving' for road answers only. Omit for every option.

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: it uses published fares with source timestamps, computes `roadConditionsNow` against America/New_York, explains source caveats for links that don't publish data, and clearly states the tool provides published patterns not live incidents. This is thorough and honest about limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, dense paragraph of ~300 words. It is front-loaded with an overview and contains valuable details, but it lacks clear structure or brevity. Some sentences could be trimmed (e.g., the repeated emphasis on 'without a car'). It earns its place content-wise but is not concise or easy to scan.

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?

Despite no output schema, the description gives a comprehensive picture: what modes are covered, how fare data is sourced, how `roadConditionsNow` works, how `to` affects output, and explicit caveats about source attribution and lack of live data. For a tool with this complexity, the description is remarkably complete.

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?

The schema provides descriptions for both parameters, and the description adds meaningful details beyond them. For `to`, it explains the output effect (reports Jitney stops and drive-time rows with typical AND summer minutes). For `mode`, it mostly restates the schema but reinforces 'car-free' as the right choice for without a car. This is helpful but not a huge leap beyond the structured data.

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 the tool's purpose: how to get to the East End and around it, covering specific transit modes (Hampton Jitney, LIRR, ferries, etc.) and driving. It explicitly says to call this for any getting-there, how-long, how-much, or when-should-I-leave question, distinguishing it from sibling tools about beaches, parking, or events.

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?

The description gives explicit usage guidance: call for any travel question, pass `to` with the asker's own destination words, pass `mode: 'car-free'` for someone without a car. It also clarifies when NOT to use the tool ('There is no live incident feed behind this'), preventing misuse.

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