Skip to main content
Glama

list_followable_zones

Read-onlyIdempotent

List the event lists (nationwide / each region / each kind) and the new-arrivals list that a user can follow. Following a list delivers notifications of new events in it. Pass an entry's type and slug to toggle_favorite (target_type = type, token = slug) to follow or unfollow it.

Coverage: a wider list includes narrower ones. Following nationwide (all/all) already covers every region and kind, so do not also follow a region on top of it. all/<area> covers every kind in that region, <kind>/all covers that kind in every region.

By default only single-axis lists are returned. Pass kind and/or area to also get the combinations for them (e.g. kind=book_club returns book clubs nationwide and in each region, plus the wider lists that cover them), or combinations: true for every combination.

Filtering by kind or area leaves out the new-arrivals (creation_zone) entry.

With a Bearer token that has favorites:read, each entry also carries following (true/false) and covered_by (the slug of a wider list the user already follows that includes it, or null). covered_by is set even when following is true, which means the follow is redundant.

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_followable_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoReturn the lists for this region of Japan (lowercase slug, e.g. "kanto", "kansai"): every kind in that region plus the wider lists covering it. Combine with `kind` to narrow further. Omit for every region.
kindNoReturn the lists for this event kind: that kind nationwide and in each region, plus the wider lists covering them (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, period_event = multi-day exhibitions / fairs). Omit for every kind. An unknown value returns an error result with `error: "invalid_argument"`.
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.
combinationsNotrue = also return every kind x region combination (about a hundred entries); false (default) = only the single-axis lists: nationwide, each region, each kind. Prefer `kind` / `area` to get just the combinations you need.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / area / description
      Previous value: -"Narrow to lists for this region."New value: +"Return the lists for this region of Japan (lowercase slug, e.g. \"kanto\", \"kansai\"): every kind in that region plus the wider lists covering it. Combine with `kind` to narrow further. Omit for every region."
    • changedInput schema / properties / combinations / description
      Previous value: -"Include every kind x region combination. Default: false."New value: +"true = also return every kind x region combination (about a hundred entries); false (default) = only the single-axis lists: nationwide, each region, each kind. Prefer `kind` / `area` to get just the combinations you need."
    • changedInput schema / properties / kind / description
      Previous value: -"Narrow to lists for this event kind (\"period_event\" = exhibitions / fairs)."New value: +"Return the lists for this event kind: that kind nationwide and in each region, plus the wider lists covering them (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, period_event = multi-day exhibitions / fairs). Omit for every kind. An unknown value returns an error result with `error: \"invalid_argument\"`."
    • 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."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely non-obvious behavior on top: the coverage lattice (all/all covers everything), the side effect that filtering drops the creation_zone entry, the auth requirement (Bearer token with favorites:read) that changes the response shape, and the subtle `covered_by` semantics where it is populated even when `following` is true.

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?

The information is front-loaded and every paragraph carries a distinct fact (destination tool, coverage rules, expansion, auth-dependent fields). It loses a point only for mild duplication of the kind/area expansion rules that the schema descriptions already spell out, and for awkward mid-sentence line breaks.

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 does the heavy lifting by explaining `type`, `slug`, `following`, and `covered_by`, plus the locale fallback caveat. It does not enumerate the remaining entry fields (names/titles), but the shape is inferable and the calling-relevant behavior is fully covered.

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% and the enum docs are already rich, so the baseline is 3. The description still adds meaning the schema does not: that the default returns only single-axis lists, that kind/area implicitly pull in the covering wider lists, and that the filters exclude the new-arrivals entry — real behavioral coupling rather than restatement.

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 the event lists (nationwide / each region / each kind) and the new-arrivals list that a user can follow'. This clearly separates it from list_events / list_apps siblings, which return content rather than followable targets, and names the downstream consumer (toggle_favorite) 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?

Gives an explicit next step ('Pass an entry's `type` and `slug` to toggle_favorite (target_type = type, token = slug)') plus an explicit when-not rule ('do not also follow a region on top of nationwide'). It also states when to use `kind`/`area` versus `combinations: true`, so the alternative paths are all disambiguated.

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