Skip to main content
Glama
koizumikento

JMA Data MCP

by koizumikento
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

search_nearby_stations

Find AMeDAS weather stations within a specified radius of given coordinates. Provide latitude and longitude to locate nearby stations for accessing JMA data.

Instructions

Search AMeDAS stations within a radius from given coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude in decimal degrees
lonYesLongitude in decimal degrees
radius_kmNoSearch radius in kilometers (default: 50)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / lat / description
      Added value: +"Latitude in decimal degrees"
    • addedInput schema / properties / lon / description
      Added value: +"Longitude in decimal degrees"
    • addedInput schema / properties / radius_km / description
      Added value: +"Search radius in kilometers (default: 50)"
  2. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided; description lacks information on edge cases like no results, data freshness, or result limitations, leaving agent unaware of behavioral traits.

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?

Single, front-loaded sentence with no extraneous words; highly concise and efficient.

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?

Description is adequate for a simple search tool with output schema present, but does not clarify return format or result details, relying on schema for completeness.

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% with clear parameter descriptions; description adds no additional semantics beyond what schema already provides.

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?

Clearly specifies verb 'Search', resource 'AMeDAS stations', and scope 'within a radius from given coordinates', effectively distinguishing from sibling tools like list_stations.

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?

Usage is implied by the description, but no explicit guidance on when to use this tool versus alternatives such as search_stations or list_stations.

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