Skip to main content
Glama
Sign In

Hamptons Verified

by com.hamptonsverified
OverviewDiscussionsAdmin

Urgent care, pharmacy and the ER, open now?

urgent_care
Read-onlyIdempotent

Where to go for care on the East End, 10 verified facilities: the hospital emergency department, urgent care, pharmacies and the emergency vet, each with openState, closesAt and opensAt computed from the published hours line against the East End's clock (America/New_York), and phone. The list holds one emergency department, in Southampton, and one 24/7 emergency vet, in Riverhead. coverage.completeness describes how complete the list is: it is a short verified list, not a directory, so a town absent from it is a gap in coverage, not evidence that there is no care there. verifiedDaysAgo is the age of the hours check and hoursConfidence flags a stale one. verdictCaution appears where the hours line carries a qualifier the guide could not resolve ("seasonal extended"). sourceCaveat appears because all records are filed against a single source URL. Nothing returned is medical advice. With town, facilities in that town sort first and nothing is filtered out. townScope reports how the place argument was read; townScope.recognized: false means the name matched no East End place, the rows array is empty, and didYouMean lists near matches where any exist.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "urgent_care"
  }
}

Input Schema

NameRequiredDescriptionDefault
needNo`er` (hospital emergency department), `urgent-care`, `pharmacy`, `vet` (emergency vet). Omit for all four.
townNoThe asker's town or hamlet ('Montauk', 'Sag Harbor'). Facilities in that town sort first; nothing is filtered out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / need / description
      Previous value: -"`er` (hospital emergency department), `urgent-care`, `pharmacy`, `vet` (emergency vet). Omit to get all four, the whole list is 10 facilities."New value: +"`er` (hospital emergency department), `urgent-care`, `pharmacy`, `vet` (emergency vet). Omit for all four."
    • changedInput schema / properties / town / description
      Previous value: -"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."New value: +"The asker's town or hamlet ('Montauk', 'Sag Harbor'). Facilities in that town sort first; nothing is filtered out."
  2. Changed1 schema field changed
    • changedInput schema / properties / need / description
      Previous value: -"`er` (hospital emergency department), `urgent-care`, `pharmacy`, `vet` (emergency vet). Omit to get all four — the whole list is 10 facilities."New value: +"`er` (hospital emergency department), `urgent-care`, `pharmacy`, `vet` (emergency vet). Omit to get all four, the whole list is 10 facilities."
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond that: openState/closesAt/opensAt are computed against America/New_York, verifiedDaysAgo is the age of the hours check, hoursConfidence flags staleness, verdictCaution marks unresolved qualifiers, and sourceCaveat exists because all records share one source URL. It also discloses the closed-world list limit (one ED in Southampton, one 24/7 vet in Riverhead) and that a missing town is a coverage gap, which is exactly the kind of caveat an agent needs.

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 purpose is front-loaded and nearly every sentence carries non-redundant information, which matters because there is no output schema to document the return shape. It loses a point for density: long comma-chained sentences pack field-level documentation into a single block, making it slower to scan than necessary.

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?

With no output schema and no annotation detail on return values, the description supplies the full picture: which fields appear, how they are computed, what the caveat fields signal, and how filtering versus sorting behaves. Nothing an agent needs in order to call this correctly and interpret the response is missing.

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 100% and both parameters are already documented, so the baseline would be 3. The description goes further by explaining how `town` is actually read: matching places sort first and nothing is filtered out, and townScope.recognized:false means the rows array is empty with didYouMean near matches — semantics an agent cannot infer from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first clause names a concrete task and resource: 'Where to go for care on the East End', then enumerates the four facility types and the count (10 verified facilities). That is enough for an agent to separate it from generic siblings like whats_open_now or find_shops, though no sibling is named explicitly, which keeps it short of a 5.

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

Usage Guidelines3/5

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

The use case is implied by 'Where to go for care' and the coverage caveat warns that absent towns are a gap rather than proof of no care, which is real guidance on interpretation. However, there is no explicit when-to-use/when-not-to-use routing against siblings such as whats_open_now, and no statement that a true emergency should not be resolved via this tool beyond the 'not medical advice' disclaimer.

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