Skip to main content
Glama

get_place

Read-onlyIdempotent

Get a single Zindies place (shop/venue) by token, with address, geo coordinates, place type, zines available there, and business hours. area is the JP region slug of the place (null when unknown) and zones the event lists for that region and nationwide (empty when the region is unknown): where to look for ZINE events around this shop. business_hours (null when the place has published nothing about its hours) carries status_now (open / closed / unknown, same judgement as the web page badge), regular (free-text hours / holidays / special notes as written by the place) and calendar (the place's day-by-day calendar for this month and next: days lists only dates the place has set, each with state open / open2 / closed, a symbol (○ / ◎ / ✕), opening times and is_open; months[].legend explains the symbols, months[].note carries the month's remark and ics_url is an iCal feed of the same calendar for subscribing). A date missing from calendar.days has no day-specific setting: fall back to regular, do not treat it as closed. Use this to answer "is this shop open on (date)?" without fetching the web page.

events points at the place's events: url (the upcoming-events page) and calendar, a subscribable iCal feed of upcoming events (ics_url, webcal_url for Apple Calendar / Outlook, google_calendar_url to add it to Google Calendar). The place thus has two distinct feeds: opening days (business_hours.calendar.ics_url) and events (events.calendar.ics_url). When the user asks to import or subscribe to a shop's events in their calendar, give them events.calendar; for the event list itself use list_events_by_place.

event_proposals is non-null only when the place has said it is open to people proposing an event to hold there: terms (what the place wrote about its space and conditions; may be null) and contact_url (the page where a creator or another shop starts that conversation). null means the place has not said so on Zindies — it is not a refusal; do not tell the user the place rejects events. 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": {
      "token": "<token>"
    },
    "name": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesPublic token of the place.
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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description does add real behavioral context beyond them: null-vs-refusal semantics for event_proposals, the rule that dates absent from calendar.days mean 'no setting' rather than closed, and the distinction between the two iCal feeds. That is useful, but padded with backtick-heavy field narration that could be tighter.

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 description is front-loaded and information-dense, but it runs to six paragraphs of prose with heavy inline backtick notation. Several sentences are repetitive or expanded explanations of response fields rather than actionable guidance, making it longer than necessary for 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 the entire return-value burden, and it does: it documents business_hours status/regular/calendar internals, the symbol legend, both ICS feeds, zones, events and event_proposals. An agent can interpret the response without opening a schema.

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 the baseline is 3. The description adds a small amount of meaning about output structure but no additional semantics for the input parameters, so it stays close to the baseline. That said, the extensive field explanations provide useful context for interpreting the response.

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?

The first sentence states a specific verb and resource ('Get a single Zindies place (shop/venue) by token') and immediately enumerates what comes back: address, geo coordinates, place type, zines, business hours. Sibling tools are implicitly separated by noting that the event list itself is handled by list_events_by_place.

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?

It gives an explicit use case ('Use this to answer "is this shop open on (date)?" without fetching the web page'), routes the event-list need to list_events_by_place, and instructs on follow behavior ('follow only when the user asks') versus list_followable_zones. It also warns against a specific misreading of null event_proposals.

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