Skip to main content
Glama
loosephoto

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sat_tle

Retrieve Two-Line Element (TLE) orbital data for satellites such as ISS, Hubble, weather satellites, or Tiangong by name or NORAD ID.

Instructions

任意の人工衛星（ISS・ハッブル・気象衛星・中国宇宙ステーション等）の軌道要素(TLE)を返す。

例:「ISSの軌道要素」「ハッブル宇宙望遠鏡のTLE」「気象衛星の軌道」
認証不要。CelesTrak（NORADカタログ）から取得。
content に表示用サマリ、structuredContent に JSON（軌道パラメータ）を返す。

Args:
    name: 衛星名または省略名（例 "iss", "hubble", "tiangong", "goes-18"）。
        **和名は英語名/既知名へ自動解決**する（"ひので"→29479, "ひまわり9号"→41836,
        "宇宙ステーション"→iss）。解決できない場合は既知の名前を提示して停止する。
    norad_id: NORAD カタログ番号（例 25544=ISS）。name より優先。
    group: CelesTrak の衛星グループ（例 "stations", "weather", "amateur", "science"）。
    limit: 返す件数（既定 5、最大 20）。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
groupNo
limitNo
norad_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the data source (CelesTrak/NORAD), that no auth is needed, the return shape (content summary plus structuredContent JSON), name-resolution behavior for Japanese names, and that unresolved names stop with suggestions. It omits rate-limit/error nuances but is substantially more informative than typical.

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?

Purpose and examples are front-loaded, and the return-format line precedes the parameter docs. The example list is slightly redundant with the parameter examples, but overall it is efficient and well-organized.

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?

For a read-only lookup with no output schema, the description explains the return structure, the data source, the no-auth posture, and the failure behavior on unresolved names. Nothing an agent needs to invoke it correctly appears to be missing.

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 fully: name (with examples and Japanese-name auto-resolution), norad_id (with 25544=ISS example and explicit precedence over name), group (CelesTrak groups), and limit (default 5, max 20). Every parameter's meaning and constraints are supplied.

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 TLE orbital elements for arbitrary satellites, with concrete examples (ISS, Hubble, weather sats, Chinese station). The TLE-specific scope distinguishes it from siblings like satellite_status or sat_ground_track without needing to name them.

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 conveyed only implicitly through example queries ("ISSの軌道要素", "ハッブルのTLE"), and it notes no authentication is required. There is no explicit when-to-use vs. when-not guidance or reference to the competing sibling tools, leaving the agent to infer selection.

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