Skip to main content
Glama
Sign In
space-finder-mcp

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

space_weather

Retrieve solar flares, CMEs, geomagnetic storms, and solar particle events from NASA DONKI, plus NOAA SWPC forecasts, to monitor current space weather conditions.

Instructions

NASA DONKI の宇宙天気（太陽フレア・CME・地磁気嵐・太陽粒子現象）を返す。

例:「最近の太陽フレア」「CME(コロナ質量放出)の情報」「地磁気嵐は起きてる?」

Args: kind: データ種別 - "all": 太陽フレア・CME・地磁気嵐・太陽粒子をまとめて表示（既定） - "flare": 太陽フレア(FLR) - "cme": コロナ質量放出(CME) - "gst": 地磁気嵐(GST) - "sep": 太陽高エネルギー粒子現象(SEP) - "forecast": 予報（フレアの発生確率 C/M/X 級・活動領域（黒点群）別の確率・ NOAA 3日予報の予想最大 Kp と S/R スケール確率・公式の根拠文）。 DONKI は予報を提供しないため NOAA SWPC から取得する（出典を明記） start_date: 開始日（YYYY-MM-DD）。省略時は既定（最近）。forecast では使わない。 end_date: 終了日（YYYY-MM-DD）。省略時は既定。forecast では使わない。 limit: 各カテゴリの返す件数（既定 10、最大 20）。forecast では活動領域の表示数。

Input Schema

NameRequiredDescriptionDefault
kindNoall
limitNo
end_dateNo
start_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.41.4
    • removedInput schema / properties / end_date / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / end_date / default
      Removed value: -null
    • removedInput schema / properties / end_date / title
      Removed value: -"End Date"
    • addedInput schema / properties / end_date / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / start_date / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / start_date / default
      Removed value: -null
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
    • addedInput schema / properties / start_date / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"space_weatherArguments"
  2. Addedv0.25.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses the upstream source (NASA DONKI), the forecast exception (NOAA SWPC with source noted), the limit cap, and the forecast-specific parameter behavior. It leaves the default 'recent' date range vague and does not cover error or rate-limit 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?

Front-loads the purpose in one sentence, then uses compact examples and a structured Args section. Every part contributes useful selection or invocation guidance without repetition.

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?

Given no output schema and no annotations, the description is thorough enough for correct invocation: all parameters, sources, defaults, and the forecast special case are covered. It could be more complete by specifying the exact default date window and output fields, but the essential calling information is present.

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 compensate, and it does: it defines every parameter, enumerates all kind values with defaults, explains date formatting, and notes that start_date/end_date are not used for forecast. It also clarifies limit's default, maximum, and forecast-specific 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?

States a specific verb and resource: returns NASA DONKI space-weather data covering flares, CMEs, geomagnetic storms, and SEPs. The listed categories and examples make the tool distinguishable from general astronomy/weather siblings.

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?

Provides concrete example queries and maps each kind value to its data category, including the important forecast exception. It does not explicitly compare against sibling tools such as astronomy_weather, but the intended usage is clear.

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