Skip to main content
Glama

Agoreta: where and when

Opening hours of a venue

opening_hours
Read-onlyIdempotent

Finds a venue by name (optionally near a point or in a city) and returns its regular weekly opening hours: listed, or an estimate (basis=estimate).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "opening_hours"
  }
}

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).
nameYesVenue name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the description's added value is the disclosure that results may be either listed hours or an estimate (basis=estimate) — an important data-quality caveat the agent would otherwise miss. It also scopes the return to 'regular weekly' hours rather than exception/holiday hours, which sets expectations. It stops short of saying what happens when the venue cannot be matched.

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?

A single front-loaded sentence with no filler, and the output caveat is packed into a compact trailing clause. The colon-separated return detail is slightly dense but still readable and earns its place.

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 no output schema and five parameters, the description carries the right extras: the result concept (weekly hours), the estimate fallback, and the locator options. Remaining gaps are minor — it does not describe the shape of the returned hours or how a missing venue is reported.

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 every parameter is already documented in the schema; the baseline of 3 applies. The description restates the locator options (name, point, city) but adds nothing about the 'at' parameter, which is the one field whose purpose (evaluating hours for a specific moment) is not echoed anywhere in the 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 gives a concrete verb+resource ('Finds a venue by name ... returns its regular weekly opening hours') and specifies the lookup scope (by name, optionally near a point or in a city). It is clearly distinguishable from a generic search, though it never contrasts itself with the close sibling 'open_now', leaving the agent to infer the boundary between weekly hours and current status.

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 only implied: an agent can infer this is the tool for a venue's regular weekly schedule, and the parenthetical clarifies which locator forms are acceptable. There is no explicit when-to-use/when-not statement and no named alternative (e.g. 'open_now' for current status), so routing between the two relies on guesswork.

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