Skip to main content
Glama
tysonwu

norikae-mcp

by tysonwu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_routeA

Search train routes between stations in Japan using Yahoo! Transit.

IMPORTANT: Station names MUST be in Japanese kanji/kana. Convert before calling:

English → Japanese:

  • Tokyo → 東京, Shinjuku → 新宿, Shibuya → 渋谷, Ikebukuro → 池袋

  • Ueno → 上野, Akihabara → 秋葉原, Ginza → 銀座, Roppongi → 六本木

  • Yokohama → 横浜, Osaka → 大阪, Kyoto → 京都

  • Narita Airport → 成田空港, Haneda Airport → 羽田空港

Chinese (Simplified/Traditional) → Japanese kanji:

  • 东京/東京 → 東京, 新宿 → 新宿, 涩谷/澀谷 → 渋谷

  • 秋叶原/秋葉原 → 秋葉原, 横滨/橫濱 → 横浜 Note: Japanese kanji may differ from Chinese hanzi (e.g., 渋 vs 涩/澀, 横 vs 横/橫)

Examples:

  • "Tokyo to Shinjuku" → from: "東京", to: "新宿"

  • "从东京到新宿" → from: "東京", to: "新宿"

  • "Shibuya to Ikebukuro via Harajuku" → from: "渋谷", to: "池袋", via: ["原宿"]

Options summary:

  • timeType: departure(出発), arrival(到着), first_train(始発), last_train(終電), unspecified(指定なし)

  • ticket: ic(ICカード), cash(きっぷ)

  • seatPreference: non_reserved(自由席), reserved(指定席), green(グリーン車)

  • walkSpeed: fast(急いで), slightly_fast(少し急いで), slightly_slow(少しゆっくり), slow(ゆっくり)

  • sortBy: time(到着が早い順), transfer(乗換回数順), fare(料金安い順)

  • useAirline, useShinkansen, useExpress, useHighwayBus, useLocalBus, useFerry: true/false

Prompts

Interactive templates invoked by user choice

NameDescription
norikae-usageInstructions for using the Japanese train route search tool

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no ambiguity or overlap with other tools. The purpose of search_route is clear and unique.

Naming Consistency5/5

The single tool name 'search_route' follows a clean verb_noun pattern. Consistency is trivially maintained with only one tool.

Tool Count3/5

The server has exactly one tool for a very focused domain. While not excessive, it feels thin for a route search service that might benefit from supporting tools like station lookup or route alternatives.

Completeness4/5

The search_route tool covers the core route search functionality with extensive options (time, ticket, seat, walk speed, sort order, and transit mode filters). However, there are minor gaps such as no station information or direct comparison of multiple routes.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources