Skip to main content
Glama

Agoreta: where and when

When a place is busiest

rhythm
Read-onlyIdempotent

Estimates how busy the surroundings of a point are by hour of a day of the week (index against the place's weekly average, level 1-5, people rounded to tens), the peak hours, and the busiest spots nearby. Always an 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": "rhythm"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoMoment to evaluate, ISO 8601. Without an offset it is the local time of the place. Default: now.
dayNoDay of the week. Default: the day of `at` (today).
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).
hourNoHour of the day (local). Default: the hour of `at` (now); with `day` alone the whole day is returned.
radius_mNoRadius for the busiest spots nearby. Default 1500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description focuses instead on what the numbers mean: an index against the place's weekly average, a 1-5 level, people rounded to tens, plus a candid 'Always an estimate' caveat. That is meaningful behavioral context beyond the annotations, missing only detail on latency or coverage limits.

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?

A single dense sentence that front-loads the primary output and then lists the secondary returns, with the estimate caveat placed last for emphasis. No filler.

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, the description does the necessary work of describing the return shape (index, level, peak hours, nearby spots). Seven optional parameters are fully specified in the schema, so remaining gaps are minor.

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 including defaults and ranges is already documented in the schema. The description hints at the hour/day dimension and the nearby-spots radius but adds no format or interaction detail beyond what the schema provides.

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 ('estimates') and resource ('how busy the surroundings of a point are'), and it also enumerates the three outputs: hourly busyness index, peak hours, and nearby busy spots. It is unambiguous what the tool does, though it never contrasts itself with siblings like 'open_now' or 'opening_hours'.

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 guidance on when to reach for this tool versus alternatives such as 'events' or 'open_now', and no stated prerequisites. The description is purely about output content, so the agent must infer the use case itself.

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