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, hair salons, 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "restaurant",
      -  "breakfast",
      -  "nightlife",
      -  "wine",
      -  "wellness",
      -  "ice-cream",
      -  "farm-stand",
      -  "oyster-farm"
      -]New value: +[
      +  "restaurant",
      +  "breakfast",
      +  "nightlife",
      +  "wine",
      +  "wellness",
      +  "salon",
      +  "ice-cream",
      +  "farm-stand",
      +  "oyster-farm"
      +]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: result ordering (closing-soonest-first), returned fields (closesAt, address, phone, source + verified date), result cap of 10, and precise semantics for hoursUnknown, publishedHoursOnly, opensNext, seasonalClosureRisk, and townScope. It even explains the reasoning behind seasonal exclusion (stale summer hours).

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?

Dense and long, but front-loaded with the core purpose and usage trigger, then layered with edge-case handling. Nearly every sentence earns its place, though the seasonal-closure passage is somewhat sprawling and could be tightened.

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 exists, so the description must explain the return shape — and it does, covering ordering, fields, counts, and fallback arrays. Combined with the usage routing and seasonal caveats, an agent has everything needed to call and interpret this tool correctly.

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 50%, and the description compensates well: it describes townScope.recognized/didYouMean behavior for the town parameter and confirms region-vs-hamlet handling. It lists categories that map to the enum, adding little beyond the schema there, but the town-side semantics exceed the schema.

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?

States a specific capability — what is open in an East End town right now and until when, computed against the region's own timezone. It also enumerates the covered venue categories and clearly separates itself from sibling tools that handle events, beach info, or planning.

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?

Explicitly routes the call: 'Call this for anything phrased as now, right now, still open, tonight, this late.' It also gives conditional usage rules — read seasonalClosureRisk from November to April, treat townScope.recognized:false as a not-found rather than 'nothing is open', and use opensNext when little is open.

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.

Resources