Skip to main content
Glama
Sign In
loosephoto

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

eodashboard_collections

Search Earth observation datasets from NASA, ESA, and JAXA by theme, agency, or keyword to find relevant satellite and climate data without authentication.

Instructions

EO Dashboard（NASA・ESA・JAXA共同）の地球観測データセットを検索する（認証不要）。

例:「NASAの大気データ」「気候変動の衛星データ」「NO2 のデータセット」

Args: themes: テーマ（例 "atmosphere", "oceans"）。カンマ区切りで複数可。 agency: 機関（例 "NASA", "ESA", "JAXA"）。 keyword: キーワード（タイトル・説明に部分一致）。 limit: 返す件数（既定 20、最大 50）。

Input Schema

NameRequiredDescriptionDefault
limitNo
agencyNo
themesNo
keywordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv0.41.4
    • removedInput schema / properties / agency / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / agency / default
      Removed value: -null
    • removedInput schema / properties / agency / title
      Removed value: -"Agency"
    • addedInput schema / properties / agency / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / keyword / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / keyword / default
      Removed value: -null
    • removedInput schema / properties / keyword / title
      Removed value: -"Keyword"
    • addedInput schema / properties / keyword / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / themes / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / themes / default
      Removed value: -null
    • removedInput schema / properties / themes / title
      Removed value: -"Themes"
    • addedInput schema / properties / themes / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"eodashboard_collectionsArguments"
  2. Addedv0.25.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that authentication is not required and that limit defaults to 20 with a maximum of 50. It does not describe return fields, pagination, or error behavior beyond that.

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 purpose is front-loaded, query examples are practical, and the Args section efficiently covers the parameters. It is appropriately sized for a search tool, with little wasted text.

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?

It is sufficient to invoke the tool, but with no output schema and no annotations it leaves the return shape and pagination behavior unexplained. It also does not explain how this differs from eodashboard_detail or the other collection-search siblings.

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

Parameters4/5

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

Schema description coverage is 0%, so the description has to compensate, and it documents all four parameters: themes, agency, keyword, and limit. It adds useful semantics such as comma-separated themes, partial matching for keyword, and limit bounds, though accepted theme values remain only examples.

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?

It states a clear verb and resource: searching EO Dashboard Earth observation datasets, with the specific NASA/ESA/JAXA joint source. It does not explicitly distinguish itself from sibling collection/search tools such as copernicus_collections or jaxa_datasets.

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 examples imply when the tool is useful, and it notes that no authentication is required. However, it gives no explicit when-not-to-use guidance or routing to alternatives, which matters given the many sibling dataset-search tools.

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