Skip to main content
Glama
Sign In
JMA Data MCP

JMA Data MCP

by koizumikento
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search Stations

search_stations
Read-onlyIdempotent

Find AMeDAS stations by Japanese, Kana, or English name to identify locations for JMA weather observations and forecasts.

Instructions

Search AMeDAS stations by name (Japanese, Kana, or English).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "search_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesStation name to search

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 / name / description
      Added value: +"Station name to search"
  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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description usefully adds that multiple script forms are accepted, which annotations can't convey. It says nothing about whether matching is exact or partial, how many results come back, or ordering.

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

Conciseness3/5

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

A single front-loaded sentence with no filler, which is good. It is arguably under-specified rather than concise: the brevity comes at the cost of matching semantics and guidance rather than from tight editing.

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?

With an output schema present, return values needn't be explained, and annotations cover safety. Still, for a search tool the description leaves the core behavior (match type, result limits, what happens on no match) unstated, so an agent must experiment to call it confidently.

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?

Only one parameter and schema coverage is 100%, so the schema documents the input adequately and the baseline of 3 applies. The description adds value by saying the name may be Japanese, Kana, or English, but gives no detail on exact vs. partial matching or ambiguity handling.

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 (search) plus the resource (AMeDAS stations) and the matching key (name), and clarifies the accepted script forms (Japanese, Kana, English). An agent can distinguish it from list_stations or get_stations_of_type 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 Guidelines3/5

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

The description implies usage ('search by name'), which is enough to know you need a name, but it never states when to prefer this over search_nearby_stations, get_stations_of_type, or list_stations. No exclusions or alternatives are offered despite several plausible siblings.

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