Skip to main content
Glama

Japan Toilet & Accessibility

by com.gachi-tokusuru.api

get_station_context

Read-onlyIdempotent

Same official municipality data as get_municipality_context, resolved from a station: pass a station name (Shinjuku / 新宿 / Musashi-Kosugi) or a Japan Station Master station_id (e.g. st_00001), and it returns the context for that station's municipality. Official values only — no scores.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoOptional comma-separated subset: vacancy,ridership,population,hazard,land_price,livability.
station_idNoJapan Station Master station_id (e.g. st_00001). Alternative to station_name.
station_nameNoStation name in English/romaji (Shinjuku) or Japanese (新宿). Provide this or station_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hazardNoHazard categories.
stationNoResolved station.
vacancyNoHousing-vacancy counts.
ridershipNoRidership trend.
land_priceNoLand prices near the centroid.
livabilityNoLivability counts.
populationNoPopulation / future estimate.
attributionNoData source(s), license and provenance — an object, or an array of sources.
municipalityNoMunicipality + code.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds that it provides 'official values only — no scores', which enriches understanding of returns without contradicting annotations.

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 sentences, front-loaded with purpose and reference to sibling. No extraneous words. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present (as per context signals), description need not detail return values. It covers resolution logic, input formats, and data source. Complete for a simple lookup tool with good annotations.

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 100%, so schema already describes all parameters. Description adds minor clarification: station_name can be English/romaji or Japanese, and station_id format example (e.g. st_00001). Baseline 3, slight value but not significantly more.

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?

Description clearly states it returns the same municipality data as get_municipality_context but resolved from a station. Specifies input types (station name or ID) and output scope (official values only, no scores). Distinct from siblings like get_municipality_context.

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?

Explicitly describes how to use: pass a station name or station_id. References the sibling get_municipality_context as an alternative, implying this is the station-based version. Lacks explicit when-not-to-use guidance but sufficient context.

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

All Japan Toilet & Accessibility toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation2/5

Several tools have overlapping purposes: get_active_alerts and get_station_alerts both return JMA flood/landslide alerts, differing only by input type. Similarly, get_municipality_context and get_station_context expose the same underlying data via different resolvers, and get_station_context already includes hazard categories that get_station_hazard duplicates in more detail. These overlaps make it difficult for an agent to know which tool to select for a given query.

Naming Consistency4/5

Most tools follow a clear 'get_' prefix (e.g., get_toilet_by_station, get_train_status), which is consistent. However, 'station_search' and 'ping' break the pattern, and the role-split text references a non-existent 'search_ramen' tool. The dominant convention is clear, but the exceptions introduce minor inconsistency.

Tool Count4/5

With 10 tools, the count is within a reasonable range for the server's broad scope (station info, toilet accessibility, hazards, alerts, train status). However, the redundancy between municipality_context/station_context and actives_alerts/station_alerts means not every tool earns a unique place, making the set slightly over-provisioned. Still, it is not excessively large.

Completeness3/5

The server covers the main info-retrieval needs for toilets, station hazards, alerts, and train status. However, station_search explicitly tells agents to 'search_ramen' for ramen details, yet that tool is not provided, creating a clear dead end. Also, the domain is broader than the server name suggests, and some peripheral data (e.g., detailed ramen profiles) is only partially surfaced.

Resources