JMA Data MCP

List Stations

list_stations

Read-onlyIdempotent

Retrieve paginated AMeDAS station listings (1,286 stations) from Japan's weather network. Use limit and offset to find station identifiers for observations, forecasts, or historical data.

Instructions

List all AMeDAS stations (1286 stations) with pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_stations"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of stations to return (default: 100)
`offset`	No	Number of stations to skip (default: 0)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.2.1May 1, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum number of stations to return (default: 100)"
```
- addedInput schema / properties / offset / description
```
Added value: +"Number of stations to skip (default: 0)"
```
First observedDec 19, 2025

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds the total station count (1286) and pagination behavior, which helps an agent plan iteration, but says nothing about ordering of results or what happens if limit exceeds the total.

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?

A single front-loaded sentence with zero filler; scope, count, and pagination are all stated immediately.

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

Completeness4/5

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

An output schema exists and annotations cover the safety profile, so the description need not explain return values. The remaining gap is routing guidance against the many sibling search tools, which keeps it from a 5.

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 description coverage is 100% with defaults documented for both limit and offset, so the schema carries the parameter burden. The description only echoes 'with pagination' and adds no syntax or bounds beyond that.

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?

States a specific verb and resource plus useful scope detail (all AMeDAS stations, 1286 total). The word 'all' implicitly separates it from search_stations, but no sibling is named outright, so differentiation rests on inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'list all' hints that this is the unfiltered enumeration path versus search_stations or get_station_info, but no explicit when/when-not guidance or alternative is stated.

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

Deploy Server