Skip to main content
Glama
Sign In
jaxa-earth-mcp

jaxa-earth-mcp

by a-hikata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_datasets

Search JAXA Earth API datasets by keyword or list major datasets without one. Finds precipitation, land surface temperature, vegetation, elevation, soil moisture.

Instructions

JAXA Earth API のデータセットを検索する。

keyword を省略すると主要データセット(降水/地表面温度/植生/地形/土壌水分)を返す。 keyword を与えると STAC カタログ全体を ID 部分一致で検索する (例: "GSMaP", "GCOM-C LST", "AW3D30")。

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

Input Schema

NameRequiredDescriptionDefault
keywordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description discloses the two operational modes and references the STAC catalog, sufficiently covering behavioral traits for a read-only list tool.

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 sentences with no wasted words; purpose stated first, then details, all in a clear and efficient structure.

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 simple single-parameter search tool with no output schema, the description covers all necessary aspects: when to use each mode, example inputs, and implicit return of dataset lists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description fully compensates for 0% schema coverage by explaining the keyword parameter's effect in both modes and providing concrete examples, adding substantial meaning.

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?

The description clearly states the tool searches JAXA Earth API datasets, distinguishes behavior with and without keyword, and provides examples, effectively differentiating from sibling tools.

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?

The description tells when to use keyword (to search specific datasets) and when not (to get major datasets), but does not explicitly exclude other scenarios or compare with 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