odpt_resolve_station
Pack: odpt · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/odpt_resolve_station for the schema, then POST the same URL with its arguments for the data.
Find a Japan train station by name, in English or Japanese (“Shinjuku” or “新宿”), and return its ODPT station id(s), operator, railway and coordinates — for looking up Japanese railway/metro stations (Tokyo Metro, JR East, Toei and other operators). ODPT has no name-search endpoint, so this fetches station master data for the given operator (or a short list of major Tokyo operators if none is given) and matches client-side — one station can have several ids, one per operator/railway that serves it. Use the returned station_id with odpt_station_timetable. Needs an ODPT developer consumer key via _apiKey; Pipeworx supplies one if omitted. Example: odpt_resolve_station({ query: “Shinjuku” }).
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
query | string | yes | Station name in English or Japanese, e.g. “Shinjuku” or “新宿”. |
operator | string | no | Limit to one operator, e.g. “Tokyo Metro”, “JR East”, “Toei”, or an exact odpt.Operator id. Default: searches several major Tokyo operators. |
limit | number | no | Max matches to return, 1-50. Default 10. |
_apiKey | string | yes | Optional: your own ODPT developer consumer key. Pipeworx supplies one if omitted. |
Example call
Arguments
{
"query": "Hakusan",
"operator": "Toei"
}
curl
curl -X POST https://gateway.pipeworx.io/odpt/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"odpt_resolve_station","arguments":{"query":"Hakusan","operator":"Toei"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('odpt_resolve_station', {
"query": "Hakusan",
"operator": "Toei"
});
Response shape
| Field | Type | Description |
|---|---|---|
source | string | |
query | string | |
count | number | |
stations | array | |
data_as_of | string |
Full JSON Schema
{
"type": "object",
"properties": {
"source": {
"type": "string"
},
"query": {
"type": "string"
},
"count": {
"type": "number"
},
"stations": {
"type": "array",
"items": {
"type": "object",
"properties": {
"station_id": {
"type": "string"
},
"name_ja": {
"type": "string"
},
"name_en": {
"type": "string"
},
"operator": {
"type": "string"
},
"railway": {
"type": "string"
},
"station_code": {
"type": "string"
},
"lat": {
"type": "number"
},
"lon": {
"type": "number"
}
},
"additionalProperties": true
}
},
"data_as_of": {
"type": "string"
}
},
"additionalProperties": true
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the odpt pack
{
"mcpServers": {
"odpt": {
"url": "https://gateway.pipeworx.io/odpt/mcp"
}
}
}
See Getting Started for client-specific install steps.