Skip to main content
Glama
loosephoto

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

jaxa_dataset_search

Search JAXA Earth datasets by keyword to find satellite data such as GSMaP rainfall, ALOS elevation, or GCOM sea surface temperature. No authentication required.

Instructions

JAXA Earth のデータセットをキーワード検索する（認証不要）。

例:「GSMaPの降雨データ」「ALOSの標高データ」「GCOMの海面水温」
content に表示用サマリ、structuredContent に JSON を返す。

Args:
    query: 検索語（例 "GSMaP", "ALOS", "GCOM", "precip", "rain", "FNF", "AW3D"）。
    limit: 返す件数（既定 10、最大 100）。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that authentication is not required and describes the return structure (content summary plus structuredContent JSON), but omits pagination, rate limits, and error behavior.

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?

The description is front-loaded with purpose, followed by example queries, return format, and an Args section. Every sentence adds useful information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple no-auth search tool with no output schema, the description covers purpose, parameters, and return format well. It lacks only sibling differentiation and pagination behavior, which are minor gaps for calling the tool correctly.

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?

Schema description coverage is 0%, so the description must document parameters. It does so fully: query is explained with domain-specific examples, and limit is documented with its default (10) and maximum (100), adding constraints not present in the schema.

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?

States a specific verb ('キーワード検索') and resource ('JAXA Earth のデータセット'), plus notes authentication is not required. It does not explicitly differentiate this from the sibling jaxa_datasets or other dataset search tools.

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 through query examples ('GSMaP', 'ALOS', 'GCOM') and the no-auth note. No explicit when-to-use versus alternatives or when-not-to-use guidance is provided.

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