Skip to main content
Glama

list_events

Read-onlyIdempotent

List upcoming and ongoing Zindies events (festivals, fairs, exhibitions). DayEvent (single-day) and PeriodEvent (multi-day) are unified, distinguished by event_type. Default range: today through 60 days ahead.

The response carries zone: the event list on Zindies these results come from (nationwide, a region, a kind, or both), with type, slug, name and url. get_event returns the lists a single event appears in (zones). zone is an event list on Zindies (name, url) that you can point the user to for more events like these. Lists can be followed: pass type and slug to toggle_favorite (target_type = type, token = slug) and new events in the list are delivered to the user. Mention a list once if it helps; follow only when the user asks. list_followable_zones lists every list and whether the user already follows it.

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
toNoRange end (YYYY-MM-DD). Default: from + 60 days.
areaNoFilter by JP region (lowercase slug). Also matches events that only have a prefecture in that region.
fromNoRange start (YYYY-MM-DD). Default: today.
kindNoFilter by event kind. `period_event` means multi-day exhibitions / fairs (the same as event_type: period; search returns this kind for them).
limitNoMaximum number of events to return. Default 20, max 50.
localeNoResponse language for translatable text fields (names, titles, descriptions). Pass the language the user is conversing in when it is one of the supported locales. Fields without a translation fall back to their source language. Default: ja.
event_typeNoRestrict by event type.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Filter by event kind."New value: +"Filter by event kind. `period_event` means multi-day exhibitions / fairs (the same as event_type: period; search returns this kind for them)."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "non_genre",
      -  "zine_making",
      -  "author",
      -  "festival_style",
      -  "zine_cafe",
      -  "book_club",
      -  "utakai"
      -]New value: +[
      +  "non_genre",
      +  "zine_making",
      +  "author",
      +  "festival_style",
      +  "zine_cafe",
      +  "book_club",
      +  "utakai",
      +  "period_event"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / area / description
      Previous value: -"Filter by JP region."New value: +"Filter by JP region (lowercase slug). Also matches events that only have a prefecture in that region."
  3. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of events to return. Default 20, max 50."
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds real behavioral context on top: a concrete default time window (60 days ahead), locale fallback behavior, and the follow-delivery side effect of toggle_favorite. It does not discuss pagination/ordering of results beyond `limit`, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentences are well front-loaded, but the second paragraph defines `zone` twice in near-identical terms ("The response carries `zone`..." and "`zone` is an event list on Zindies (`name`, `url`)..."), wasting space. The follow-mechanics sentence chain is dense and could be tightened.

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 takes on explaining the return payload and does describe the `zone` object's fields and how to cross-reference via get_event. It stops short of describing the event object itself (fields, ordering), but for a filtered list tool over a well-documented schema this is close to complete.

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 all seven parameters are already documented, and the description largely restates what the schema says (default range, period_event meaning). It adds marginal interpretation around how `kind: period_event` relates to `event_type: period`, but no syntax or precedence guidance for combining area/kind/event_type filters.

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 ("List upcoming and ongoing Zindies events") plus the covered entity types (festivals, fairs, exhibitions) and the DayEvent/PeriodEvent unification. It is clearly about listing events, but it does not contrast itself with the sibling listers (list_events_by_creator, list_events_by_place), so sibling differentiation is only partial.

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?

Provides the default range (today through 60 days) and operational guidance on the `zone` object -- mention once if helpful, follow only when the user asks, toggle_favorite arguments, and pointer to list_followable_zones. It never states when to prefer this tool over list_events_by_creator / list_events_by_place or when a single-event lookup (get_event) is the better call, so usage is implied rather than fully routed.

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