Skip to main content
Glama

get_event

Read-onlyIdempotent

Get a single Zindies event by id, with its host (place, organizer_creator, or organizer = an organizing body such as a festival committee), registered creators, reserved booths, programs (workshops, talks and other sessions held within the event), and source_posts (the organizer's own Instagram or note posts introducing exhibitors who are not in booths; these people have no Zindies page, so link to url for details). zones lists the event lists this event appears in, narrowest first (kind in its region, its region, its kind nationwide, nationwide); it is empty when the event is not on the public lists. Each entry in zones 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

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": {
      "id": "<id>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric ID of the event.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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, so safety is covered. The description adds genuine behavioral context beyond that: zone ordering is narrowest-first, zones is empty when the event is not publicly listed, and source_posts people have no Zindies page so the `url` must be surfaced — all operationally important for correct use.

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 purpose and return fields are correctly front-loaded, but the description is a single dense paragraph where list-following workflow guidance (the last three sentences) occupies a large share of the text for one getter. Content earns its place, but the length is disproportionate to a two-parameter read tool.

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 the description must carry return-value semantics — and it does, explaining each nested field, the zone ordering, and the empty-zones case. An agent has everything needed to call this correctly and interpret what comes back.

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 both `id` and `locale` are already documented in the schema, including the enum and ja default. The description only implies id-based lookup and says nothing about locale fallback behavior; the `type`/`slug` discussion refers to toggle_favorite's parameters, not this tool's. 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+resource ('Get a single Zindies event by id') and then enumerates exactly what is returned (host variants, registered creators, booths, programs, source_posts, zones). This clearly separates it from list_events, list_events_by_creator, and search, which operate on collections rather than a single id.

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 explicit downstream guidance: when zones is empty, how to use `type`/`slug` with toggle_favorite, and the policy 'mention a list once if it helps; follow only when the user asks'. It does not state the inverse case (what to do when you lack an id, e.g., use search), so the coverage is strong but not complete.

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