Skip to main content
Glama

Can you drink the tap water here?

tap_water

Whether the tap water is drinkable, hamlet by hamlet, from the guide's read of the water utility's and the state health department's own reporting. Call this for any drink-the-water, tap, well, filter, bottled-water, PFAS, 1,4-dioxane or is-the-water-safe question, and call it before reassuring anybody, because the East End does not have one answer: three of the hamlets covered are private-well territory (Springs, Shelter Island, Southold) where NO agency tests the water and the only honest answer is "ask your host for the last test result", and Wainscott's story — PFOS and PFOA in more than 150 private wells, then a main extension in December 2018 that put the hamlet on public water — is one a model reliably garbles into a warning about the wrong contaminant or a hamlet-wide all-clear. Every safe here is about PUBLIC water only. verdict is the guide's own paragraph for that hamlet: read it out rather than reducing it to yes or no. status comes with statusMeaning so you never have to infer what the word covers, and filterRecommendation names a certification rather than a brand — with filterCaveat alongside it wherever the guide's own glossary has since corrected which NSF/ANSI number covers PFAS, which is the difference between the right filter and the wrong one. sources are the citable links with the date each was read, and they carry two things no model holds: SCWA's June 2025 declaration of full compliance with the federal PFOA/PFOS limits six years early, and the Stage 1 Water Alert declared across the East End on 14 July 2026 — a drought conservation request whose own notice says supply and quality are unaffected, so never repeat it as a health warning. utilities names who actually pipes the water and the number to ring; it deliberately carries no URL, because the guide's filed links for those records no longer resolve and a dead citation is worse than none. noVerdictHeld names a place the guide has not written up — say that plainly instead of reading the next hamlet's verdict across. Pass a hamlet, a region, or the ZIP off the lease. With no argument nothing is looked up: you get the hamlets covered, so ask which one. Never tell anyone their own private well is safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
placeNoWhere they are: a hamlet ('Montauk', 'Springs', 'Wainscott'), a region ('the Hamptons', 'North Fork'), or a ZIP ('11937'). Pass the asker's own words.

TDQS

A4.6/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 explains that 'safe' refers only to public water, identifies private-well hamlets, warns about model-garbling of Wainscott's story, and details what each output field contains. It also clarifies the Stage 1 Water Alert is not a health warning and gives the rationale for omitting URLs in `utilities`. This goes far beyond a typical description.

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 well-structured and front-loaded with the core purpose. Each section adds value, though some redundancy exists (e.g., repeating the private-well warning in different forms). It earns a 4 rather than 5 due to its length and some repetitive phrasing.

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?

No output schema means the description must explain return values, and it does thoroughly: `verdict`, `status`/`statusMeaning`, `filterRecommendation`/`filterCaveat`, `sources`, `utilities`, and `noVerdictHeld` are all described. It also covers edge cases like private wells and unsupported places, making it complete for complex real-world queries.

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

Parameters3/5

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

The schema already provides thorough documentation for the single `place` parameter, including examples and instruction to pass the asker's words. The description reinforces the optionality and adds a usage note ('With no argument...'), but does not add significant new semantic information beyond the schema. Baseline 3 is appropriate.

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 opens with a precise statement: 'Whether the tap water is drinkable, hamlet by hamlet, from the guide's read of the water utility's and the state health department's own reporting.' It further lists explicit trigger phrases ('drink-the-water, tap, well, filter...'), distinguishing it from siblings like beach_info or whats_open_now.

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?

It provides explicit when-to-use guidance: 'Call this for any drink-the-water, tap, well, filter, bottled-water, PFAS, 1,4-dioxane or is-the-water-safe question, and call it before reassuring anybody.' It also instructs on the no-argument case: 'With no argument nothing is looked up: you get the hamlets covered, so ask which one.' This is strong usage guidance.

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