Skip to main content
Glama

Eventstatapp

List upcoming events

list_events
Read-onlyIdempotent

Lists upcoming and ongoing events with live status pages on Eventstatapp, soonest first. Optionally search by name or location words and limit to a date range. Returns each event's slug, dates, location, current status and links.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMost events to return (1–100, default 25).
queryNoWords to look for in the event name or location, e.g. "marathon" or "Richmond". Leave out to list all.
to_dateNoOnly events starting on or before this day (YYYY-MM-DD).
from_dateNoOnly events still running on or after this day (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description adds genuinely new context: result ordering, the fact that only events with live status pages are included, and the shape of returned fields. Pagination/rate-limit behavior is left unstated, keeping it short of a 5.

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?

Three tight sentences: purpose and ordering first, optional filtering second, return contents third. No filler, and the ordering detail is front-loaded where an agent will see it.

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 usefully enumerates the returned fields (slug, dates, location, status, links), and the annotations cover the safety profile. A simple four-param list tool needs little more, though noting anything about result limits beyond the limit param would complete it.

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% and each parameter carries its own description, so the schema does the heavy lifting. The description's 'search by name or location words' and 'limit to a date range' restate rather than extend the schema's semantics.

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?

States a specific verb and resource ('Lists upcoming and ongoing events with live status pages'), plus scope and ordering ('soonest first'). The list-vs-detail distinction from get_event_status/get_event_updates is inferable but not explicitly stated.

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 single word 'Optionally' signals that query and date filtering are discretionary, and the schema clarifies that omitting query lists all. There is no explicit when-to-use vs when-to-use-alternatives guidance or mention of the sibling tools.

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