Skip to main content
Glama

What's open right now

whats_open_now

What is actually open in an East End town at this moment, and until when — computed from verified opening hours against the East End's own clock (America/New_York), not yours and not UTC. Call this for anything phrased as now, right now, still open, tonight, this late: you cannot know it, and the clock you would reason from is the wrong one. Results are ordered closing-soonest-first and each carries closesAt, address, phone, and its source with the date we last verified it. Covers restaurants, breakfast, nightlife, wine, wellness, ice cream, farm stands and oyster farms. hoursUnknown counts venues in that town whose hours the guide does not hold — they were not considered, so never present the list as everything that is open — and publishedHoursOnly names the ones that publish an hours line we have not parsed, so you can offer them separately and attributed rather than dropping them. When little or nothing is open — late at night, or off-season, which is when this gets asked — opensNext comes back with the venues that open soonest and when, so answer with those and never let it end at "nothing is open". From November to April read seasonalClosureRisk before you answer: venues verified as NOT year-round are held OUT of the open list, because the hours they leave published are the summer table and computing an open-now verdict from it in February is how an assistant sends someone to a shut clam shack. They are not claimed closed either — the guide holds no closing date — so name them as seasonal, say we cannot confirm they are trading this month, and give the phone. It is also why a winter answer is short: most of what a July answer would list is in that array, not absent. Returns up to 10. townScope.recognized: false means the name matched no East End place at all — that empty answer is a not-found, NOT "nothing is open": say the name was not recognised and offer didYouMean.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
townYesA hamlet ('Sag Harbor', 'Montauk') or a whole region ('the Hamptons', 'the North Fork', 'the East End') — a region is answered across every hamlet in it. Pass the asker's own words.
categoryNo

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 carries full burden and does so thoroughly. It discloses timezone handling, result ordering, response fields (closesAt, address, phone, source), the meaning of hoursUnknown and publishedHoursOnly, seasonalClosureRisk behavior from November to April, the fact that seasonal venues are excluded but not claimed closed, and the 10-result limit. This is exemplary transparency.

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

Conciseness5/5

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

The description is long but dense and front-loaded. The first sentence delivers the core purpose and timezone; subsequent paragraphs add necessary edge cases. Every sentence earns its place, with no fluff or repetition, and the structure moves logically from general behavior to specific warnings.

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 having no output schema, the description thoroughly explains return fields, ordering, unknown/parsed hours handling, seasonal exclusions, opensNext fallback, and unrecognized-town semantics. It covers all critical behaviors an agent needs for correct invocation and response interpretation, making it complete for this 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 50% (only town has a description). The description compensates somewhat by listing covered categories ('restaurants, breakfast, nightlife, wine, wellness, ice cream, farm stands and oyster farms'), which mirrors the category enum. However, it does not explain region handling for town, category optionality, or how to translate the prose list to enum values, so the compensation is partial.

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 'What is actually open in an East End town at this moment, and until when — computed from verified opening hours against the East End's own clock', giving a specific verb, resource, and scope. It clearly distinguishes this from siblings like recently_closed and search_places by focusing on current open status and closing times.

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 explicitly says 'Call this for anything phrased as now, right now, still open, tonight, this late' and warns against reasoning from a wrong clock. It also provides exclusions and edge-case guidance: never present a list as exhaustive when hours are unknown, never end with 'nothing is open' when opensNext exists, and how to handle unrecognized towns via townScope.recognized.

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