Skip to main content
Glama

joino Japan Events

Build car navigation URLs

build_navigation_url
Read-onlyIdempotent

Build car navigation URLs (Google Maps, Apple Maps, Waze, etc.) via chosen event venues. 選んだイベント会場を経由地に含むカーナビURLを生成する(6サービス対応)。

Google Maps、Apple Maps、Yahoo!カーナビ、Waze、HERE WeGo、MapFanの URLを一括生成して返す。

Args: origin: 出発地(地名・住所) destination: 目的地(地名・住所) waypoint_addresses: 経由地の住所リスト(最大10箇所) event_ids: Optional event ids (from search results) to show as waypoints on the joino.me route page

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>",
      "waypoint_addresses": "<waypoint_addresses>"
    },
    "name": "build_navigation_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYes
event_idsNo
destinationYes
waypoint_addressesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 openWorldHint, so safety is covered. The description adds genuinely useful behavior: six services are generated in one call and waypoints are capped at 10. But it says nothing about failure modes (unresolvable addresses), URL length limits, or what happens when the 10-waypoint cap is exceeded.

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 English paragraph is front-loaded and efficient, but the entire content is then repeated in Japanese, roughly doubling length without adding information. The Args block earns its place since schema coverage is 0%, but the bilingual duplication is pure redundancy.

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?

For a read-only URL builder with an existing output schema, the definition covers purpose, supported services, and all four parameters well enough to invoke it correctly. Remaining gaps are edge-case behaviors (invalid addresses, the 10-waypoint cap) rather than anything blocking a correct call.

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 0%, so the description carries the full burden, and it does document all four parameters, including the formats ('地名・住所') and the max-10 waypoint limit. It still leaves gaps: the format of event_ids (string ids from which result field), whether waypoint_addresses may be empty, and how event_ids interact with waypoint_addresses on the route page.

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 description names a specific verb and resource ('Build car navigation URLs') and enumerates the concrete outputs (Google Maps, Apple Maps, Yahoo!カーナビ, Waze, HERE WeGo, MapFan), plus the 'via event venues as waypoints' scope. An agent can immediately tell this is a URL-construction tool, distinct from the search-oriented siblings.

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 only implied: the mention that event_ids come 'from search results' and 'on the joino.me route page' hints at a preceding search step, and 'via chosen event venues' hints at waypoint selection. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative among the sibling search tools.

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