Skip to main content
Glama
Sign In
loosephoto

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

neo_close_approach

Retrieve upcoming near-Earth asteroid and comet close approaches. Filter by date range, distance, object type, and hazardous status to assess potential Earth flyby risks.

Instructions

小惑星・彗星の地球接近（近地球天体の接近イベント）を返す（認証不要・APIキー不要）。

例:「今日/今週地球に接近する小惑星」「危険な小惑星の接近予報」「月距離以内に来る天体」

Args: days: 何日先までを見るか（1〜365、既定 7）。 max_distance_au: 接近距離の上限（au、既定 0.05 ≒ 19.5 月距離。0.00256 au ≒ 1 LD）。 limit: 表示する最大件数（1〜50、既定 10）。接近時刻の早い順。 hazardous_only: True なら「潜在的に危険な小惑星(PHA)」だけに絞ります。 PHA は小惑星の区分なので彗星は含めません（彗星に PHA はありません）。 kind: 対象の種別。"all"（既定＝小惑星＋彗星）/"asteroid"（小惑星のみ）/ "comet"（彗星のみ）。a/c や「小惑星」「彗星」も受け付けます。

Input Schema

NameRequiredDescriptionDefault
daysNo
kindNoall
limitNo
hazardous_onlyNo
max_distance_auNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.41.4
    • removedInput schema / properties / days / title
      Removed value: -"Days"
    • removedInput schema / properties / hazardous_only / title
      Removed value: -"Hazardous Only"
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / max_distance_au / title
      Removed value: -"Max Distance Au"
    • removedInput schema / title
      Removed value: -"neo_close_approachArguments"
  2. Changed1 schema field changedv0.39.5
    • addedInput schema / properties / kind
      Added value: +{
+  "default": "all",
+  "title": "Kind",
+  "type": "string"
+}
  3. Addedv0.39.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose that no auth or API key is required, that results are sorted by approach time (earliest first), and that hazarding is asteroid-only (comets have no PHA). It says nothing about the response shape, error behavior, or rate limits, and only vaguely says it "returns" events.

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?

Front-loaded purpose followed by a clean Args block; each sentence carries information (auth status, sort order, PHA/comet caveat). Minor redundancy in the opening parenthetical gloss of "Earth close approach," but otherwise tight.

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?

For a five-parameter, zero-annotation, no-output-schema tool, the description is nearly complete: purpose, auth, sorting, filtering semantics, and all parameter ranges/defaults. The main remaining gap is that the fields of each returned approach event are never described and there is no output schema to cover them.

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: every one of the five parameters has a range, a default, and a unit/meaning (0.00256 au = 1 LD, 0.05 au ≈ 19.5 LD), plus accepted aliases for kind ("a"/"c", Japanese words), which the schema does not enumerate.

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?

States a specific verb and resource: returns Earth close-approach events for asteroids and comets, illustrated with three example queries. It is clearly a filtered event-list tool, but never mentions the sibling neo_today (or impact_risk), so an agent cannot tell from the text alone which of the two near-Earth-object tools to pick.

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 example phrasings ("asteroids approaching Earth today/this week", "hazardous asteroid forecasts", "objects within one lunar distance") give concrete contexts in which to call it. There are no explicit exclusions or named alternatives, which keeps it at 4 rather than 5.

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