Skip to main content
Glama

Jma Past Daily

jma_past_daily
Read-onlyIdempotent

Past daily weather observations for one month at one JMA station: precipitation (total, max 1h, max 10min), mean/max/min temperature, humidity, mean wind, sunshine hours, snowfall and snow depth, plus pressure at staffed stations. One row per day, missing values null (never 0), elements the station does not observe null. Takes a station name, a station_id from jma_station_search ("48-0393") or a JMA block number. Sourced from the Japan Meteorological Agency, past weather data search (daily values).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": 2026,
      "month": 1,
      "station": "Nozawa Onsen"
    },
    "name": "jma_past_daily"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesCalendar year, e.g. 2026.
monthYesMonth 1-12.
stationYesStation name ("Nozawa Onsen"), station_id ("48-0393") or block number ("47610").
prefectureNoOptional prefecture to disambiguate a station name.

Output Schema

NameRequiredDescriptionDefault
daysNo
yearNo
foundNofalse when nothing matched; see reason
monthNo
notesNoInterpretation notes
reasonNoWhy nothing was returned
sourceNoPublisher and dataset
day_countNo
candidatesNo
data_as_ofNoDate the data is current to (ISO)
station_idNo
station_typeNo
prefecture_jaNo
station_name_jaNo
elements_presentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), it discloses genuinely useful behavior: one row per day, missing values are null and never 0, elements the station does not observe are null, and pressure is only reported at staffed stations — these prevent an agent from misreading absent data as zero.

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?

Three tight sentences, front-loaded with scope and granularity, then data-quality semantics, then provenance; no filler or repetition.

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?

Although an output schema exists, the description still supplies the interpretation rules an agent needs (null vs zero, station-specific element availability) plus granularity and source, covering everything required to call and read a 4-parameter historical-observation tool correctly.

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% and the schema already documents year, month, station formats, and the optional prefecture. The description's station-format sentence largely restates the schema and never mentions the prefecture disambiguation parameter, so it adds little meaning beyond the structured fields (baseline 3).

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?

States a specific verb and resource ('Past daily weather observations for one month at one JMA station') and enumerates the returned elements (precipitation, temperature, humidity, wind, sunshine, snow, pressure), which lets an agent tell it apart from forecast or normals tools without opening the schema.

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?

Gives concrete input-precondition guidance: the station argument accepts a name, a station_id obtained from jma_station_search, or a JMA block number. It does not explicitly state when to prefer this over jma_climate_normals or jma_forecast, so exclusions are left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.