Skip to main content
Glama

Search events

search_events
Read-onlyIdempotent

Search events in Japan by keyword, prefecture, category and date range. イベントを検索する。キーワード、都道府県、カテゴリ、日付範囲で絞り込み可能。

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": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the user's conversation: ja, en, zh or ko (default ja). Sets joino_url to the page in that languageja
limitNoMax results (1-100, default 20)
date_toNoEvents starting on or before this date (YYYY-MM-DD)
keywordNoKeyword matched against title/description/translations (Japanese or English, e.g. "花火", "fireworks")
categoryNoEvent category key(s), comma separated. See list_categories (e.g. festival, culture, sports)
date_fromNoEvents held on or after this date (YYYY-MM-DD). Default: today (ended events are excluded)
prefectureNoPrefecture in English or Japanese (e.g. "Tokyo", "Kyoto", "東京都")
include_experiencesNoAlso include year-round bookable experiences/activities (tours, workshops), listed after dated events

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Event category key(s), comma separated. See list_categories (e.g. festival, culture, sports)"
    • addedInput schema / properties / date_from / description
      Added value: +"Events held on or after this date (YYYY-MM-DD). Default: today (ended events are excluded)"
    • addedInput schema / properties / date_to / description
      Added value: +"Events starting on or before this date (YYYY-MM-DD)"
    • addedInput schema / properties / include_experiences / description
      Added value: +"Also include year-round bookable experiences/activities (tours, workshops), listed after dated events"
    • addedInput schema / properties / keyword / description
      Added value: +"Keyword matched against title/description/translations (Japanese or English, e.g. \"花火\", \"fireworks\")"
    • addedInput schema / properties / lang / description
      Added value: +"Language of the user's conversation: ja, en, zh or ko (default ja). Sets joino_url to the page in that language"
    • addedInput schema / properties / limit / description
      Added value: +"Max results (1-100, default 20)"
    • addedInput schema / properties / prefecture / description
      Added value: +"Prefecture in English or Japanese (e.g. \"Tokyo\", \"Kyoto\", \"東京都\")"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured fields. The description adds only the geographic scope (Japan), while omitting behavior the schema holds but an agent would benefit from in prose, such as the default date_from=today that silently excludes ended events and the presence of non-dated experiences.

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?

Two short sentences, front-loaded with the core verb-resource-scope, with zero filler. The second sentence is a Japanese rendering of the first rather than new information, but that duplication is plausibly intentional for a multilingual audience, so the cost is minor.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations are rich, so the description needn't explain return values. Still, for an 8-parameter optional-everything search tool, the description says nothing about the lang parameter's effect on result URLs or about include_experiences mixing year-round activities into results, leaving meaningful behavior to schema discovery.

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 every parameter including lang, limit, include_experiences and date defaults is already documented in the schema. The description merely restates four of the eight filter dimensions without adding format, default, or interaction semantics beyond that, which is the baseline 3 case.

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 (search) plus resource (events) plus scope (Japan) and enumerates the filter axes. It does not differentiate itself from siblings like search_nearby_events or search_route_events, which also return events, so the agent must infer that this is the keyword/prefecture-driven variant.

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?

The filter list implicitly signals when to reach for this tool (keyword, prefecture, category, date filters) rather than a location- or route-based sibling. However, there is no explicit when-to-use guidance, no exclusions, and no naming of the alternative tools, so the routing decision is left to inference.

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