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

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

qzss_status

Retrieve QZSS (Michibiki) orbit and augmentation signal data without authentication, plus current file lists and download URLs for clock, almanac, ephemeris, and related products.

Instructions

みちびき（準天頂衛星システム QZSS）の軌道・補強信号データを取得する（認証不要）。

例:「みちびきは今どのあたりにある？」「準天頂衛星の軌道データ」「みちびきの

Args: kind: データ種別。既定 "orbit"（QZU 超速報 軌道 SP3）。他に rapid-orbit / final-orbit / clock / erp / almanac / ephemeris / ephemeris-qzss / l1s / l6 / anpi（安否確認サービス）/ naqu。 orbit 以外は最新ファイルの一覧とダウンロードURLを返す（本体は取得しない）。 未知の種別は候補一覧を返して停止する。 count: 一覧に出すファイル数（既定 5, 最大 20）。orbit 以外で使う。 product_id: 特定のファイル ID（例 "qzu24373_18.sp3"）。省略時は最新。

Input Schema

NameRequiredDescriptionDefault
kindNoorbit
countNo
product_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.41.4
    • removedInput schema / properties / count / title
      Removed value: -"Count"
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • removedInput schema / properties / product_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / product_id / default
      Removed value: -null
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • addedInput schema / properties / product_id / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"qzss_statusArguments"
  2. Addedv0.39.0

TDQS

A3.7/5.0
Behavior3/5

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

Since no annotations are provided, the description is vital. It clearly discloses the 'authentication unnecessary' nature of the data access. However, it does not elaborate on error handling, potential data latency, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is necessary due to the complexity of the `kind` parameter, the resulting structure is dense. It is not maximally concise, but the density is a justified consequence of the tool's need to explain multiple complex behaviors based on input choices.

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?

The definition is highly complete given its purpose. It covers the functional implications of every parameter choice and the constraints of the data (e.g., the difference between data retrieval and URL listing). It only lacks a formalized description of the return data structure itself.

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?

The description excels here, offering exhaustive details on the `kind` parameter, listing every possible type and detailing the specific output associated with each. It fully explains how `count` and `product_id` interact, which is critical as schema coverage is 0%.

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 description clearly defines the tool's purpose: obtaining orbital and signal data for QZSS (Michibiki). It successfully specifies the resource and the action, but it does not explicitly state how this service differs from other general satellite tracking tools in the sibling list.

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?

The description provides strong functional guidance on how the tool operates, specifically explaining that certain 'kind' values return lists of URLs rather than direct data. However, it lacks prescriptive guidance on *when* to use this tool compared to general space weather or general satellite status lookups.

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