Hamptons Verified

Urgent care, pharmacy and the ER — open now?

urgent_care

Where to go for care on the East End right now — hospital emergency department, urgent care, a pharmacy that is still open, or the emergency vet — with openState, closesAt and opensAt computed from the published hours line against the East End's clock (America/New_York). Call this for hurt, sick, cut, tick bite, stitches, a prescription to fill, a pharmacy still open tonight, or a dog or cat in trouble. Three things here are the ones a model gets wrong from memory and cannot check: there is exactly ONE emergency department in this list and it is in Southampton — none in East Hampton, none in Montauk, so from Montauk it is the length of Route 27; the only 24/7 emergency vet is in RIVERHEAD, off the fork entirely, and inventing one nearer costs an animal's night; and whether a pharmacy shuts at 7 or at 10 tonight is a clock question in a timezone you are not standing in. Read coverage.completeness before you characterise a town: this is a short verified list, not a directory, so a town that is absent is a gap in our coverage and NEVER evidence that there is no care there — say what the guide holds and where, never "there is nothing in Montauk". verifiedDaysAgo says how old the hours check is and hoursConfidence fires when it is stale: give phone and tell the asker to ring before driving. verdictCaution appears where the line carries a qualifier we could not resolve ("seasonal extended") — a closed verdict under one is not safe to repeat. sourceCaveat appears because all of these records are filed against a single URL: cite it as where the list came from, not as the page publishing a given pharmacy's Sunday hours. Lead every answer with 911 for anything life-threatening, and never present any of this as medical advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`need`	No	`er` (hospital emergency department), `urgent-care`, `pharmacy`, `vet` (emergency vet). Omit to get all four — the whole list is 10 facilities.
`town`	No	Where the asker is ('Montauk', 'Sag Harbor'). Facilities in that town sort first; nothing is filtered out, because the nearest care is often in the next town.

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: timezone-aware computation, single ER location, 24/7 vet location, staleness indicators, verdict cautions, source caveat, and safety instructions. It warns against common model errors and explains how to interpret fields like coverage.completeness and hoursConfidence.

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 lengthy but front-loaded with purpose and packed with essential caveats. Each sentence adds value, though some phrasing could be tightened (e.g., 'a pharmacy still open tonight' repeats earlier 'pharmacy that is still open'). Overall, it is well-structured for an AI agent needing critical context.

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 covers returned fields (openState, closesAt, opensAt, verifiedDaysAgo, hoursConfidence, verdictCaution, sourceCaveat), handles edge cases (towns absent, stale hours, qualifiers), and gives action guidance (give phone, cite source, lead with 911). This is comprehensive for the tool's complexity.

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?

Schema coverage is 100% for both parameters. The description adds little beyond what the schema already provides; it maps needs to use cases but does not elaborate on parameter values or formats. 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 specific verb+resource statement: 'Where to go for care on the East End right now — hospital emergency department, urgent care, a pharmacy that is still open, or the emergency vet.' It clearly distinguishes from siblings like whats_open_now and search_places by focusing on urgent/medical care facilities with computed open status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use guidance is provided: 'Call this for hurt, sick, cut, tick bite, stitches, a prescription to fill, a pharmacy still open tonight, or a dog or cat in trouble.' This gives a clear trigger list, though it does not name specific alternative tools or state when not to use it.

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

All Hamptons Verified tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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

Need Help?