Skip to main content
Glama

Jma Climate Normals

jma_climate_normals
Read-onlyIdempotent

Official JMA climate normals (30-year averages, currently 1991-2020) for one station: for each month and the year, precipitation, mean temperature, mean daily max and min temperature, wind, sunshine and, where the station observes snow, snowfall total and mean annual-maximum snow depth. Use for questions like typical late-January snowfall or temperature at a resort. Takes a station name, station_id or block number. Sourced from the Japan Meteorological Agency, climate normals.

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": {
      "station": "Nozawa Onsen"
    },
    "name": "jma_climate_normals"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationYesStation name ("Nozawa Onsen"), station_id ("48-0393") or block number.
prefectureNoOptional prefecture to disambiguate a station name.

Output Schema

NameRequiredDescriptionDefault
foundNofalse when nothing matched; see reason
notesNoInterpretation notes
monthsNo
reasonNoWhy nothing was returned
sourceNoPublisher and dataset
candidatesNo
data_as_ofNoDate the data is current to (ISO)
station_idNo
station_typeNo
station_titleNo
normals_periodNoe.g. 1991-2020
years_of_recordNo
elements_presentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavioral context: the normalization period is currently 1991-2020, the data is sourced from JMA, and snow fields exist only where the station observes snow. It does not say what happens when a station is ambiguous or unmatched, which is the main remaining gap.

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?

The description is front-loaded with the resource and period, then the fields, then the use case – a sensible order. The variable enumeration is long but each item carries information about what comes back. No filler sentences.

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?

For a read-only lookup with an output schema, the description covers what is needed to call it correctly: input identifier forms, the data period, station-level scoping, and the conditional snow fields. Return values are handled by the output schema, so nothing essential is missing.

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%, so both parameters are already documented in the schema, including the station name/id/block-number forms. The description restates the identifier forms but adds no format details or disambiguation behavior beyond what the schema's prefecture field already conveys. 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?

The description names a specific resource and scope: official JMA 30-year climate normals for a single station, enumerating the returned variables (precipitation, mean/max/min temperature, wind, sunshine, snowfall, snow depth). That is far more specific than the title. It never names a sibling tool such as jma_past_daily, so the differentiation from related station-data tools is implied rather than stated.

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?

It gives a concrete use case – 'typical late-January snowfall or temperature at a resort' – which tells an agent the kind of question this answers. It does not state when to prefer it over alternatives (e.g. observed daily history via jma_past_daily) or when not to use it, so exclusions are left to inference.

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.