Skip to main content
Glama
Sign In
鉄道駅LOD MCPサーバー

鉄道駅LOD MCPサーバー

by uedayou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

鉄道の階層をドリルダウン(事業者→路線→駅)

list_railway_children

Fetches the railway lines belonging to a specified operator or the stations on a specified line, enabling operator→line→station drill-down in Japanese railway linked data.

Instructions

指定した事業者の路線一覧、または路線の駅一覧を取得する(wdt:P527)。事業者→路線→駅のドリルダウンに使う。

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": {
      "parent": "<parent>"
    },
    "name": "list_railway_children"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
parentYes親エンティティのラベル or URI。jrslod では事業者(例: '東日本旅客鉄道')→ 路線一覧、または路線(例: '東日本旅客鉄道/山手線')→ 駅一覧。事業者名の別名は自動補完を試みる。駅の順序が必要なときは list_stations_on_line を使う。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; '取得する' does establish this as a read-only retrieval, and citing wdt:P527 signals that results are bounded by Wikidata coverage. However, it says nothing about pagination despite a limit default of 200 / max 1000, nor about ordering of returned lines/stations or what happens when the parent label is ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the operation and followed by the use case; every clause carries information and nothing is redundant.

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?

For a simple two-parameter read tool with no output schema and no annotations, the description covers the what and the why but omits result shape, pagination behavior tied to the limit parameter, and failure modes for unknown parents. Adequate to select the tool, thin on how to invoke it well.

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 coverage is 50%: the parent parameter is richly documented (label or URI, both hierarchy modes, alias autocompletion, pointer to list_stations_on_line), while limit is undocumented. The description restates the two parent modes but adds no syntax, format, or limit semantics beyond what the schema already provides.

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?

The description states a specific verb and resource ('路線一覧、または路線の駅一覧を取得する') and names the two drill-down modes (事業者→路線、路線→駅), so an agent can tell it apart from flat list tools. It stops short of explicitly contrasting itself with siblings such as list_stations_on_line, which is only named in 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'事業者→路線→駅のドリルダウンに使う' gives a clear context of use, telling the agent this is the hierarchical traversal tool. There is no explicit when-not guidance or named alternative in the description itself; the exclusion of ordered station listings lives only in the parent parameter's schema text.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools