Skip to main content
Glama

What is open

open_now
Read-onlyIdempotent

Places open at a given moment (default now, America/New_York) in a town or category, judged only from posted hours. Verified hours are listed first. Places with unknown hours are returned separately with call_to_confirm=true and are never counted as open.

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": "open_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNo"now", "HH:MM" today (Eastern), or ISO 8601 such as 2026-11-20T18:30
townNoTown or county, e.g. "Hornell", "Watkins Glen", "Steuben County"
limitNo
categoryNoType or category: restaurant, eat_drink, bar, winery, brewery, cidery, distillery, lodging, shopping, park, trail, museum, attraction, service, health, civic, church, or a category word such as "pizza" or "bakery"eat_drink

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds real behavioral context on top: default time and timezone, data provenance limited to posted hours, ordering (verified hours first), and the unknown-hours edge case with call_to_confirm=true that is never counted as open. It stops short of describing pagination or how 'limit' affects the split results.

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?

Three short sentences, front-loaded with the core behavior, followed by ordering and edge-case handling. No filler or redundant restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four optional parameters and no output schema, the description does useful work by sketching the shape of the response (verified-first list plus a separate unknown-hours list with call_to_confirm). Only the effect of 'limit' and the returned fields remain unspecified.

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 75%, so the schema already documents time, town, limit and category. The description adds only the default timezone (America/New_York) and the town-or-category framing, which is marginal value beyond the schema; limit semantics remain unexplained in both.

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?

States a specific verb+resource: returns places open at a given moment, scoped to a town or category. It is distinguishable from lookup siblings like get_place or search_places by the openness filter, but it never names those alternatives, so the differentiation is implicit.

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?

Usage is implied rather than stated: the tool is for 'places open at a given moment' and only judges from posted hours. There is no explicit when-to-use/when-not guidance and no alternative tool is named for cases where the agent wants all places regardless of hours.

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