Skip to main content
Glama
Sign In

Tle

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Recent

list_recent
Read-onlyIdempotent

List the newest satellites in the NORAD catalog, highest catalog number first. NORAD ids are assigned in roughly launch order, so this approximates most-recently-launched. Note this orders by catalog entry, not by TLE epoch — the upstream offers no epoch-date sort.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of satellites to return. Defaults to 10.

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of satellites returned
satellitesYesArray of recently launched/updated satellites

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 15
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "satellites": {
+      "description": "Array of recently launched/updated satellites",
+      "items": {
+        "properties": {
+          "epoch": {
+            "description": "Epoch date of the TLE set",
+            "type": "string"
+          },
+          "line1": {
+            "description": "First line of the Two-Line Element set",
+            "type": "string"
+          },
+          "line2": {
+            "description": "Second line of the Two-Line Element set",
+            "type": "string"
+          },
+          "name": {
+            "description": "Name of the satellite",
+            "type": "string"
+          },
+          "norad_id": {
+            "description": "NORAD catalog ID of the satellite",
+            "type": "number"
+          }
+        },
+        "required": [
+          "norad_id",
+          "name",
+          "epoch",
+          "line1",
+          "line2"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of satellites returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "satellites"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "limit": 15
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "satellites": {
-      "description": "Array of recently launched/updated satellites",
-      "items": {
-        "properties": {
-          "epoch": {
-            "description": "Epoch date of the TLE set",
-            "type": "string"
-          },
-          "line1": {
-            "description": "First line of the Two-Line Element set",
-            "type": "string"
-          },
-          "line2": {
-            "description": "Second line of the Two-Line Element set",
-            "type": "string"
-          },
-          "name": {
-            "description": "Name of the satellite",
-            "type": "string"
-          },
-          "norad_id": {
-            "description": "NORAD catalog ID of the satellite",
-            "type": "number"
-          }
-        },
-        "required": [
-          "norad_id",
-          "name",
-          "epoch",
-          "line1",
-          "line2"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total": {
-      "description": "Total number of satellites returned",
-      "type": "number"
-    }
-  },
-  "required": [
-    "total",
-    "satellites"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "satellites": {
+      "description": "Array of recently launched/updated satellites",
+      "items": {
+        "properties": {
+          "epoch": {
+            "description": "Epoch date of the TLE set",
+            "type": "string"
+          },
+          "line1": {
+            "description": "First line of the Two-Line Element set",
+            "type": "string"
+          },
+          "line2": {
+            "description": "Second line of the Two-Line Element set",
+            "type": "string"
+          },
+          "name": {
+            "description": "Name of the satellite",
+            "type": "string"
+          },
+          "norad_id": {
+            "description": "NORAD catalog ID of the satellite",
+            "type": "number"
+          }
+        },
+        "required": [
+          "norad_id",
+          "name",
+          "epoch",
+          "line1",
+          "line2"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of satellites returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "satellites"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 15
+  }
+]
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds value by disclosing the non-obvious ordering caveat (catalog-based, not epoch-based) and its approximation quality. It doesn't discuss pagination, rate limits, or result format beyond what the output schema would provide.

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

Conciseness5/5

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

Two well-crafted sentences with zero waste. The first establishes purpose and sorting logic, the second delivers a critical caveat. Every phrase earns its place and the most important information is front-loaded.

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 tool has only one simple parameter with a default, complete annotations, and an output schema. The description covers the tool's purpose, sorting semantics, and caveats thoroughly. Given this simple complexity profile, the description is essentially complete for agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% — the single 'limit' parameter is fully documented in the input schema with its default value of 10. The description adds no semantic detail beyond the schema, so baseline 3 is appropriate per the rubric.

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?

Description clearly states it lists newest satellites in NORAD catalog by highest catalog number, which serves as a proxy for most-recently-launched. It uses a specific verb+resource combo (list satellites) with a clear sorting rationale. This distinguishes it from siblings like search_satellites and get_tle by emphasizing the catalog-order listing semantics.

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 implicitly communicates when to use this tool: when you want recent satellites via catalog number. The explicit note that it orders by catalog entry rather than TLE epoch and that upstream offers no epoch-date sort provides valuable context that prevents misuse, though it does not name specific alternative tools explicitly.

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

All Tle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources