Skip to main content
Glama

Search events along a route

search_route_events
Read-onlyIdempotent

Find events along a driving route in Japan, with car navigation URLs. ドライブルート沿いのイベントを検索し、Google Mapsカーナビ付きで返す。

出発地→目的地のルート沿いを等間隔でスキャンし、周辺イベントを収集する。 結果にはイベント一覧と、選んだイベントを経由地に含むカーナビURLが含まれる。

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "search_route_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-50, default 30)
originYesStart place name/address/station (e.g. "Tokyo Station", "東京駅")
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)
radius_kmNoSearch radius from the route in km (default 15)
destinationYesDestination place name/address/station (e.g. "Hakone", "箱根")
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. Changed10 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 / destination / description
      Added value: +"Destination place name/address/station (e.g. \"Hakone\", \"箱根\")"
    • 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-50, default 30)"
    • addedInput schema / properties / origin / description
      Added value: +"Start place name/address/station (e.g. \"Tokyo Station\", \"東京駅\")"
    • addedInput schema / properties / radius_km / description
      Added value: +"Search radius from the route in km (default 15)"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. Beyond that, the description adds real behavioral context: the route is sampled at equal intervals to collect surrounding events, and the response pairs an event list with a navigation URL embedding chosen events as waypoints — details an agent could not derive from annotations or schema.

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 purpose and the key output fact (nav URL with waypoints) are front-loaded, and the three short paragraphs are easy to scan. There is some redundancy because the English lead sentence is immediately restated in Japanese, which costs a little density without adding new meaning.

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?

An output schema exists and annotations carry the safety profile, and 100% parameter coverage means the description need not re-document inputs. What it does provide — the route-scanning model and the waypoint-bearing nav URL — fills the main gap an agent would have for a 10-parameter, route-based search tool.

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 origin/destination, radius_km, limit, lang, keyword, category and date bounds are all documented in the schema itself. The description adds no syntax or format guidance for these parameters, so the baseline 3 applies; the only implicit link is that route scanning depends on origin/destination.

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?

States a specific verb and resource (find events) with a clear mechanism: equal-interval scanning along the origin→destination driving route, returning a Google Maps car-navigation URL with selected events as waypoints. This route-based scoping is concrete enough for an agent to distinguish it from a plain point/radius event search without opening the schema.

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?

Usage is implied by the route framing (use it for origin→destination trips), and the description clarifies that year-round experiences/activities appear after dated events. However, it never names alternatives such as search_nearby_events or search_events, nor does it state when NOT to use this tool (e.g., single-location queries), leaving the selection decision 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