Skip to main content
Glama

list_stations

Retrieve a paginated list of all AMeDAS weather stations across Japan to access JMA meteorological data.

Instructions

List all AMeDAS stations (1286 stations) with pagination.

Args: limit: Maximum number of stations to return (default: 100) offset: Number of stations to skip (default: 0)

Returns: Paginated list of stations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_stations' MCP tool, decorated with @mcp.tool() for automatic registration. It implements pagination on top of get_all_stations().
    @mcp.tool()
    async def list_stations(
        limit: int = 100,
        offset: int = 0,
    ) -> dict:
        """List all AMeDAS stations (1286 stations) with pagination.
    
        Args:
            limit: Maximum number of stations to return (default: 100)
            offset: Number of stations to skip (default: 0)
    
        Returns:
            Paginated list of stations
        """
        all_stations = get_all_stations()
        paginated = all_stations[offset : offset + limit]
        return {
            "total": len(all_stations),
            "offset": offset,
            "limit": limit,
            "count": len(paginated),
            "stations": paginated,
        }
  • Helper function that loads the full list of AMeDAS stations from the local JSON data file and returns them as a list.
    def get_all_stations() -> list[dict]:
        """Get all stations."""
        stations = load_stations()
        return list(stations.values())
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it lists all stations (1286 total), supports pagination, and has default values for limit and offset. However, it doesn't cover aspects like rate limits, authentication needs, error handling, or what happens if parameters exceed bounds. It adds useful context but misses some operational details.

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?

The description is highly concise and well-structured: a single sentence states the purpose and key features, followed by clearly labeled sections for Args and Returns. Every sentence earns its place by providing essential information without redundancy, making it easy to scan and understand quickly.

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?

Given the tool's moderate complexity (2 parameters, pagination), no annotations, and the presence of an output schema (which handles return values), the description is largely complete. It covers purpose, parameters, and pagination, but could improve by mentioning sibling tools or operational constraints. The output schema reduces the need for return value explanation, keeping it adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must compensate. It provides clear semantics for both parameters: 'limit' as the maximum number to return with a default of 100, and 'offset' as the number to skip with a default of 0. This adds meaningful context beyond the bare schema, though it doesn't specify constraints like min/max values or pagination behavior details.

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?

The description clearly states the specific action ('List all AMeDAS stations') with the exact count (1286 stations) and mentions pagination, which distinguishes it from siblings like 'get_station_info' (single station) or 'search_stations' (filtered search). It uses a precise verb+resource combination that leaves no ambiguity about what the tool does.

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 description implies usage through the mention of pagination and the specific station count, suggesting it's for retrieving all stations in batches. However, it doesn't explicitly state when to use this vs. alternatives like 'search_stations' or 'get_stations_of_type', nor does it provide exclusion criteria. The context is clear but lacks direct comparative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/koizumikento/jma-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server