Skip to main content
Glama

Agoreta: where and when

Venues open at a place and time

open_now
Read-onlyIdempotent

Lists venues within a radius of a point that are open at the given moment (default: now). Hours are either listed or an estimate (basis=estimate).

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
atNoMoment to evaluate, ISO 8601. Without an offset it is the local time of the place. Default: now.
latNoLatitude (WGS 84).
lonNoLongitude (WGS 84).
cityNoCity name within a covered area; used when lat/lon are not given (the part of the city with most venues is used as the centre).
limitNoMaximum number of venues. Default 20.
categoryNoVenue category or parent category, e.g. cafe, restaurant, pub, gym, library. See sources for the list.
radius_mNoSearch radius in metres. Default 400.
include_closedNoAlso return venues that are closed at that moment. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered structurally. The description adds genuinely new behavioral context by disclosing that hours may be an estimate rather than authoritative (basis=estimate), which affects how an agent should present results. It stops short of noting rate limits, coverage gaps, or what happens when no venue matches.

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 compact sentences with zero filler: the scope-defining clause comes first and the data-quality caveat second. Every phrase earns its place and nothing is repeated from the schema or title.

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 an eight-parameter tool with no output schema, the definition is only partially complete: it hints at the hours/basis field but never describes the returned venue shape, ranking of results, or behavior when neither lat/lon nor city is supplied. The behavioral caveat is useful, but an agent must still infer substantial result structure.

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 100%, so all eight parameters carry their own descriptions and the baseline is 3. The description only reinforces the 'default: now' semantics of 'at' and introduces the estimate basis concept, adding little meaning beyond what the schema already states about at, lat/lon, city, radius_m, limit, and include_closed.

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 names a specific verb and resource ('Lists venues') plus a precise scoping condition ('within a radius of a point that are open at the given moment'), which tells an agent exactly what set of results to expect. It does not explicitly contrast itself with siblings such as opening_hours or events, so the differentiation is inferable rather than stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance: nothing says to prefer this over opening_hours when you need hours for a known venue, or over events when you want scheduled happenings. The 'default: now' phrasing hints at the primary use case but leaves the routing decision entirely to inference.

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