Skip to main content
Glama

THE COOP

by media.thecoop
OverviewDiscussionsAdmin

List events

list_events
Read-onlyIdempotent

List published iGaming event summaries with slugs, canonical URLs, dates, venue and exhibitor counts. Filter by period, region and text together. Defaults to upcoming (including ongoing), page 1, 10 records; upcoming/all sort by start date ascending, past descending. Returns page, total_items, total_pages and items. Use get_event for one event and organiser sources, or list_exhibitors for booths.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1 (default 1, maximum 500). Keep filters and limit unchanged while paging; stop at total_pages. A page beyond the results returns an empty items array.
limitNoRecords per page, from 1 to 20 (default 10). Use page to continue; total_items and total_pages describe all matches.
queryNoCase-insensitive substring in the event title or city, up to 200 characters. Omit or leave empty for all matching events; use search for semantic discovery.
periodNoupcoming (default): end_date on or after today in UTC, including ongoing events. past: end_date before today in UTC. all: no date filter.upcoming
regionNoMatch the event region exactly. Omit for all regions; combines with period and query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Records per page, from 1 to 20 (default 10). Use page to continue; total_items and total_pages describe all matches."
    • addedInput schema / properties / page / description
      Added value: +"Page number, starting at 1 (default 1, maximum 500). Keep filters and limit unchanged while paging; stop at total_pages. A page beyond the results returns an empty items array."
    • addedInput schema / properties / period / description
      Added value: +"upcoming (default): end_date on or after today in UTC, including ongoing events. past: end_date before today in UTC. all: no date filter."
    • addedInput schema / properties / query / description
      Added value: +"Case-insensitive substring in the event title or city, up to 200 characters. Omit or leave empty for all matching events; use search for semantic discovery."
    • addedInput schema / properties / region / description
      Added value: +"Match the event region exactly. Omit for all regions; combines with period and query."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent, so the description contributes defaults (upcoming, page 1, 10 records), the sort rules per period (ascending vs descending) and the response envelope (page, total_items, total_pages, items). These are non-obvious behaviors not present in the annotations or schema; only secondary details like empty-page handling are left to the schema.

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 compact sentences: purpose and payload first, then filtering/defaults/sorting, then sibling routing. No filler and nothing repeated from the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so mentioning the returned fields and paging totals is necessary and it is done. With 5 optional params all documented in the schema, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value beyond the schema by tying the period parameter to sort direction ('upcoming/all sort by start date ascending, past descending') and clarifying that filters compose — semantics the schema does not state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List published iGaming event summaries') and enumerates the payload fields (slugs, canonical URLs, dates, venue, exhibitor counts). It is clearly differentiated from get_event and list_exhibitors by name.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use get_event for one event and organiser sources, or list_exhibitors for booths.' It also states filters combine ('period, region and text together') and gives the default scope, so when-to-use is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All THE COOP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources