Skip to main content
Glama
loosephoto

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sat_ground_track

Generate an Earth map image showing any satellite's current position and ground track from its NORAD ID or name.

Instructions

任意の人工衛星の現在位置と地上軌道を地球地図にプロットした画像を返す。

例:「ISSの現在位置を地球地図で」「ひのでの位置を地図で」「ハッブルの軌道」
CelesTrak の最新 TLE を Skyfield（SGP4）で伝播し、衛星の真下の点（緯度経度・高度）
とその前後の軌道トレイルを NASA Blue Marble 地球地図に重ねる。認証不要。

精度: 軌道トレイルは step 分刻み（デフォルト 1分）で描画し、経度±180度境界で
線を分割するため、世界地図上で正確に表示される。subpoint() は地球自転・歳差・
極運動を考慮した真の地上点を返す。

Args:
    norad_id: NORAD カタログ番号（例 25544=ISS, 29479=ひので）。name より優先。
    name: 衛星名または省略名（例 "iss", "hubble", "hinode"）。既知の衛星は
        ID に解決、それ以外は TLE を直接検索。
    when: 観測時刻 ISO8601（例 "2026-09-10T03:30:00Z"）。省略で現在。
    minutes: 現在位置の前後何分の軌道を表示するか（既定 45、最大 1440=24時間）。
        準天頂衛星(みちびき)の8の字軌道を見るには 720 前後を指定。
    step: トレイルの時間刻み（分。既定 1、最小 0.5）。小さいほど滑らか。
    out_px: 出力画像の幅ピクセル（既定 1200、最大 2048）。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
stepNo
whenNo
out_pxNo
minutesNo
norad_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.2

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it names the data source (CelesTrak TLE), the propagation method (Skyfield/SGP4), states no authentication is required, explains longitude ±180 trail splitting and subpoint accuracy, and discloses the file output path plus the mandatory link behavior in content and structuredContent.image_path.

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?

Content is front-loaded — purpose first, then examples, then mechanism, accuracy notes, and finally per-argument documentation — so the reader can stop early. It is somewhat long and the accuracy paragraph is dense, but almost every sentence adds actionable detail rather than filler.

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?

Although there is no output schema, the description explains the return surface thoroughly (generated image, its saved file path, structuredContent.image_path, and the inline link for harnesses that cannot render images). Combined with documented parameter behavior, an agent has everything needed to call and present the result.

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 coverage is 0% and the description fully compensates, documenting all six parameters with defaults, ranges, and precedence: norad_id takes priority over name, name accepts abbreviations and falls back to a TLE search, when is ISO8601 with 'now' as default, minutes defaults to 45 with a 1440 cap, step default 1 / min 0.5, out_px default 1200 / max 2048.

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?

The opening sentence gives a specific verb and resource — plots any satellite's current position plus ground track onto an Earth map image, which implicitly separates it from narrower siblings like iss_now or satellite_status. It never explicitly names or contrasts a sibling tool, so it stops short of full differentiation.

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?

Concrete example queries ('ISSの現在位置を地球地図で', 'ハッブルの軌道') make the intended use obvious, and it adds situational guidance such as using minutes≈720 to see QZSS' figure-eight orbit. It offers no explicit when-not-to-use guidance or named alternatives among the many sibling tracking 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