Skip to main content
Glama

solar_eclipse_series

Creates solar eclipse progression images for any place and date, or finds the next visible eclipse. Can return a single image at maximum eclipse.

Instructions

日食の時系列パネル画像(太陽が月に欠ける過程)を返す(認証不要)。

例:「2035年9月2日の皆既日食を画像で」「東京で見える次の日食」「2019年の部分日食の進行」
指定した観測地・日付で太陽と月の視位置を JPL DE421 + Skyfield で実測計算し、
食の始まり〜最大〜終わりを複数パネルに並べて合成。月の位置角も正確に反映。

date を省略した場合は、その観測地で「これから起こる次の日食」を約4年(1400日)先まで自動検索(800日では可視の食が無い観測地があるため)。
描画するのは、その観測地で太陽が地平線より上にある時間帯だけ。最大食分も可視区間の中で
求める。全日食が地平線下なら「見えません」と明示して図は返さない(見えない食を図にして
誤解させないため。日付をまたぐ食も前後6時間まで含めて計算する)。
max_magnitude=True で最大食のみの単一画像を返す(進行でなく最も欠けた瞬間だけ見たい時)。

Args:
    date: 日付(例 "2035-09-02" / "2035/09/02" / "2035年9月2日")。省略時は次の日食を検索。
    place: 観測地(例 "東京","大阪","new york")。lat/lon 指定時は無視。省略時は東京。
    lat: 観測地の緯度。lon と併用時は place より優先。
    lon: 観測地の経度。
    max_magnitude: True で最大食のみの単一パネルを返す(既定 False=時系列)。

インライン画像を表示できないハーネス(CLI系・Android系の codex / opencode など)向けに、
content の先頭へ「🖼️ [生成した画像を開く(…)](file:///…) | 保存先: `…`」という
アイコン付きリンクを必ず出します(画像は %LOCALAPPDATA%\Temp\space_finder_mcp\out に
保存し、同じパスを structuredContent.image_path にも入れます)。
回答時はこのリンクをそのまま提示してください(画像が描画されない環境では唯一の導線)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNo
lonNo
dateNo
placeNo
max_magnitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.2

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully carries the burden of behavioral disclosure. It reveals the JPL DE421 + Skyfield calculation basis, the 1400-day search window, the visibility constraint, the behavior when a total eclipse is below the horizon, and the exact file/link output behavior. Nothing seems hidden or contradictory.

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 description is front-loaded with purpose and examples barrier to understanding, and every section serves an operational need. It is long and includes some implementation rationale, such as why 1400 days are used instead of 800, but this extra detail is still useful for setting expectations.

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?

Given no output schema and no annotations, the description covers input semantics, automatic search behavior, visibility edge cases, image generation modes, file save paths, and how the agent should present the result. An agent has enough information to invoke it correctly and interpret the response.

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%, but the description compensates by explaining every parameter: date formats, place examples, lat/lon precedence over place, defaults, and the effect of max_magnitude. This is far richer than the bare JSON schema.

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 opening sentence names a specific verb and resource: it returns time-series panel images of solar eclipses, with the Sun being obscured by the Moon. Concrete example queries further clarify scope, and the domain is clearly distinct from the generic image/space tools among 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?

The description gives operational guidance: date omission triggers an automatic next-eclipse search, max_magnitude=True selects a single-image mode, and visibility is restricted to periods when the Sun is above the horizon. It does not compare against sibling tools by name, but provides clear context for when and how to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.