Skip to main content
Glama

Agoreta: where and when

Public events near a place

events
Read-onlyIdempotent

Lists public events near a point or in a city within a date range. Each event names its organiser or publisher and licence.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD. Default: from + 7 days; at most 60 days.
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).
fromNoFirst day, YYYY-MM-DD (local). Default: today.
limitNoMaximum number of events. Default 20.
radius_mNoRadius in metres. Default 3000 around coordinates, 10000 for a city.

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one piece of real behavioral value — that results carry organiser/publisher and licence metadata — but says nothing about coverage limits, what happens when no location is supplied, or result ordering.

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 tight sentences with zero filler; the core purpose leads and the output-content note follows. Nothing is redundant or buried.

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?

For a seven-parameter, zero-required read tool with no output schema, the description covers purpose and return content adequately, and the schema handles all parameter detail. The main gap is that it never states what occurs when no location parameter is provided, which matters given that nothing is required.

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 description coverage is 100%, so every parameter (from, to, lat, lon, city, limit, radius_m) is already fully documented with defaults and bounds. The description only paraphrases those same concepts at a high level and adds no format or precedence detail beyond the schema.

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 specific verb and resource ('Lists public events') plus two scoping modes ('near a point or in a city') and a temporal bound ('within a date range'). It is clear enough to distinguish from the sibling tools (open_now, opening_hours, rhythm, sources), which cover different domains, though it does not name them explicitly.

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 by the description's mention of point-vs-city lookup; there is no explicit guidance on when to prefer city over lat/lon, no when-not-to-use condition, and no prerequisites. The useful rule about city being the fallback when lat/lon are absent lives only in the schema.

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