Skip to main content
Glama

open_now

Places in Albuquerque, NM open right now (local time), from posted hours. Filter by kind (bar, coffee, restaurant, brewery...), neighborhood, or a word like patio, kids, late, live music.

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
kindNo
limitNo
queryNo
neighborhoodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden. It does add genuine value by naming the data source ('from posted hours'), warning the agent that hours may be stale, and pinning the time reference to local time. It says nothing about result shape, what happens when nothing matches, or whether limit truncates silently.

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?

Two dense sentences, front-loaded with the scope-defining constraint before the filtering options. Every clause carries usable information and there is no filler.

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

Completeness3/5

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

For a zero-required-parameter search tool this covers intent and three of four parameters well. Without an output schema, though, nothing tells the agent what a returned place looks like (name, address, hours, rating?) or how to interpret a truncated or empty result, which leaves a real gap.

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 0%, so the description must compensate, and it largely does: it explains that kind filters by business type with concrete examples, neighborhood filters geographically, and query accepts free words like patio/kids/live music. Only 'limit' (default 15) goes unexplained in both schema and description.

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 description states a specific resource and constraint: places in Albuquerque, NM that are open right now according to posted hours. That 'open now' scoping plus the local-time note clearly differentiates it from a general place search, though it never names a sibling such as search_places to make the boundary explicit.

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 filter examples (bar, coffee, restaurant, brewery / neighborhood / patio, kids, late, live music) give a good implicit sense of what to pass for exploratory intent. However, there is no statement about when to prefer this over search_places or weekly_nights, and no exclusions or prerequisites.

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