Skip to main content
Glama
Sign In
JMA Data MCP

JMA Data MCP

by koizumikento
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Current Weather

get_current_weather
Read-onlyIdempotent

Retrieve current weather observation data from AMeDAS stations by station code, or fetch all stations when no code is provided.

Instructions

Get current weather observation data from AMeDAS stations.

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": "get_current_weather"
  }
}

Input Schema

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

Output 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description only adds that these are AMeDAS *observation* readings (measured, not modeled) — useful but thin; it says nothing about freshness/latency, missing-station behavior, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no waste. It is efficient but arguably too terse for the sibling set it lives in, leaving room for a routing clause at no structural cost.

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?

With an output schema present, rich annotations, and full parameter documentation, the description need not explain return values. The only meaningful omission is a pointer to the forecast/location/historical siblings an agent must choose between.

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% and the single parameter's meaning plus its default-to-all-stations behavior is fully documented in the schema. The description adds no parameter-level information, so the baseline 3 applies.

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 ('Get') and resource ('current weather observation data'), and the word 'current' implicitly separates it from get_forecast and get_historical_weather. It never names those siblings explicitly, so differentiation is left partly to 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 adjective 'current' implies when this is appropriate versus forecast or historical lookups, but the description gives no explicit when-to-use/when-not statement and never routes to get_weather_by_location or get_forecast. Usage is only implied.

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

Deploy Server

Other Tools