Skip to main content
Glama
koizumikento

JMA Data MCP

by koizumikento
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

get_current_weather

Retrieve current weather observations from AMeDAS stations across Japan. Provide a station code for a specific location, or omit to return data for all stations.

Instructions

Get current weather observation data from AMeDAS stations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
station_codeNoStation code (e.g., '44132' for Tokyo). If not specified, returns data for all stations.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / station_code / description
      Added value: +"Station code (e.g., '44132' for Tokyo).\n          If not specified, returns data for all stations."
  2. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states it returns 'current weather observation data' but does not mention update frequency, caching, authentication requirements, or if the data is real-time. This lacks necessary behavioral context.

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 a single, front-loaded sentence that conveys the core purpose efficiently with no wasted words.

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

Completeness3/5

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

Given the tool has only one optional parameter and an output schema exists, the description could be more complete by explaining when to use this over similar tools or what data fields are returned. It is adequate but has clear gaps.

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% as the only parameter (station_code) has a description in the schema. The description adds no additional meaning beyond what is already in the schema, so baseline score of 3 applies.

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 verb 'Get' and the specific resource 'current weather observation data from AMeDAS stations.' It distinguishes itself from siblings like get_forecast (which provides forecasts) and get_historical_weather.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as get_forecast or get_weather_by_location. The description does not mention specific contexts or exclusions.

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