tokyo-open-data-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_accessible_toiletsA | Find nearest listed wheelchair-accessible toilets in Tokyo facilities and railway stations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another tool in the set. Its purpose is clearly distinct by default.
The single tool follows a clear snake_case verb_noun pattern: find_accessible_toilets. With only one name there is no inconsistency.
A single tool is very thin for a server named tokyo-open-data-mcp, which suggests a broader open-data surface. The count is appropriate only if the server is intentionally scoped to accessible toilet lookup.
The surface covers nearest wheelchair-accessible toilet lookup but lacks supporting operations such as retrieving facility details, listing/filtering by area or station, or accessing other Tokyo open-data resources. This creates significant gaps for the apparent server scope.