Skip to main content
Glama

list_events_by_place

Read-onlyIdempotent

List upcoming and ongoing Zindies events held at a specific place (shop/venue), identified by its public token. Same semantics and response shape as list_events, but scoped to one place. Default range: today through 60 days ahead.

The response also carries calendar: a subscribable iCal feed of this place's upcoming events (ics_url, plus webcal_url for Apple Calendar / Outlook and google_calendar_url to add it to Google Calendar). When the user wants to import, subscribe to, or sync a place's events into their calendar app, hand them these URLs instead of copying events one by one — the feed stays up to date as the place adds events. Note this is distinct from the place's opening-days calendar (business_hours.calendar.ics_url on get_place).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "place_token": "<place_token>"
    },
    "name": "list_events_by_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day of the range, inclusive (YYYY-MM-DD, e.g. "2026-12-31"). Default: `from` + 60 days. For one specific day pass the same date as `from`. A value earlier than `from` returns no events.
fromNoFirst day of the range, as an ISO 8601 calendar date in Japan time (YYYY-MM-DD, e.g. "2026-12-05"; no time or timezone part). Default: today. A multi-day event already under way on this day is included. A past date returns past events. An unparseable value falls back to the default.
kindNoReturn only events of this kind (non_genre = general ZINE event, zine_making = ZINE-making workshop, author = author event (talk, signing), festival_style = fair / market with many booths, zine_cafe = ZINE cafe, book_club = book club, utakai = tanka poetry gathering). Omit for every kind. Combined with `event_type` and the date range by AND.
limitNoMaximum number of events to return, soonest first. Default 20, max 50. There is no cursor: when `count` equals `limit` there may be more, so call again with `from` set to the start date of the last event returned.
localeNoResponse language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese. Pass the language the user is conversing in when it is one of these; otherwise omit it. Fields without a translation fall back to their source language (usually Japanese), so one response can mix languages. Tokens, ids, dates and URLs are the same in every locale. Default: ja.
event_typeNo`day` = single-day events (they have `started_at` / `ended_at`), `period` = multi-day exhibitions and fairs (`start_date` / `end_date`), `all` = both (default). Combined with the other filters by AND.all
place_tokenYesPublic token of the place: a short lowercase string such as "fqpi", the `token` field of a place from search, find_places_nearby, get_place or an event's `place.token`. Not the numeric `id` or the shop name. An unknown or non-public token returns an error result with `error: "not_found"` (a place with no matching events returns `events: []`, not an error).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / event_type / description
      Previous value: -"Restrict by event type."New value: +"`day` = single-day events (they have `started_at` / `ended_at`), `period` = multi-day exhibitions and fairs (`start_date` / `end_date`), `all` = both (default). Combined with the other filters by AND."
    • changedInput schema / properties / from / description
      Previous value: -"Range start (YYYY-MM-DD). Default: today."New value: +"First day of the range, as an ISO 8601 calendar date in Japan time (YYYY-MM-DD, e.g. \"2026-12-05\"; no time or timezone part). Default: today. A multi-day event already under way on this day is included. A past date returns past events. An unparseable value falls back to the default."
    • changedInput schema / properties / kind / description
      Previous value: -"Filter by event kind."New value: +"Return only events of this kind (non_genre = general ZINE event, zine_making = ZINE-making workshop, author = author event (talk, signing), festival_style = fair / market with many booths, zine_cafe = ZINE cafe, book_club = book club, utakai = tanka poetry gathering). Omit for every kind. Combined with `event_type` and the date range by AND."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of events to return. Default 20, max 50."New value: +"Maximum number of events to return, soonest first. Default 20, max 50. There is no cursor: when `count` equals `limit` there may be more, so call again with `from` set to the start date of the last event returned."
    • changedInput schema / properties / locale / description
      Previous value: -"Response 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."New value: +"Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese. Pass the language the user is conversing in when it is one of these; otherwise omit it. Fields without a translation fall back to their source language (usually Japanese), so one response can mix languages. Tokens, ids, dates and URLs are the same in every locale. Default: ja."
    • changedInput schema / properties / place_token / description
      Previous value: -"Public token of the place (e.g. \"fqpi\")."New value: +"Public token of the place: a short lowercase string such as \"fqpi\", the `token` field of a place from search, find_places_nearby, get_place or an event's `place.token`. Not the numeric `id` or the shop name. An unknown or non-public token returns an error result with `error: \"not_found\"` (a place with no matching events returns `events: []`, not an error)."
    • changedInput schema / properties / to / description
      Previous value: -"Range end (YYYY-MM-DD). Default: from + 60 days."New value: +"Last day of the range, inclusive (YYYY-MM-DD, e.g. \"2026-12-31\"). Default: `from` + 60 days. For one specific day pass the same date as `from`. A value earlier than `from` returns no events."
  2. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of events to return. Default 20, max 50."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, and the description still adds substantial context on top: the default window (today through 60 days ahead), the pagination model (no cursor; when count equals limit, re-call with from set to the last event's start date), and the extra `calendar` payload with ics_url, webcal_url and google_calendar_url. That is behavior an agent could not infer from the structured fields.

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

Conciseness4/5

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

Front-loaded: what it lists, how it is scoped, and the default range land in the first two sentences. The second paragraph on the iCal feed is long but contains an actionable instruction rather than filler; it could be trimmed slightly without loss.

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?

With seven parameters, three enums and no output schema, the description covers the gap by defining the response shape (same as list_events, plus a `calendar` object) and its pagination contract. Error cases (not_found vs empty events) live in the schema, so nothing an agent needs in order 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.

Parameters3/5

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

Schema description coverage is 100%, and the per-parameter descriptions are unusually detailed (date semantics, enum meanings, limit/pagination, locale fallback). The prose only restates the default range and that the place is identified by its public token, adding little beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb and resource ("List upcoming and ongoing Zindies events held at a specific place") plus the identifier mechanism (public token). It explicitly anchors itself against the sibling list_events ("Same semantics and response shape ... but scoped to one place"), so an agent can separate it from list_events and list_events_by_creator without opening any schema.

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

Usage Guidelines4/5

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

Gives a concrete routing rule for the calendar-feed case: when the user wants to import, subscribe or sync a place's events, hand over the URLs instead of copying events one by one. It also draws a clear boundary against get_place's opening-days calendar. It never states a "when not to use / use X instead" clause for the plain listing case, so it stops short of a full 5.

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