Tle

Search Satellites

search_satellites

Read-onlyIdempotent

Search for satellites by name or keyword. Returns matching satellites with their NORAD IDs and TLE data.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results to return. Defaults to 10.
`query`	Yes	Name or keyword to search for (e.g. "ISS", "Starlink", "GPS").

Output Schema

Name	Required	Description
`query`	Yes	Search query that was executed
`total`	Yes	Total number of matching satellites found
`satellites`	Yes	Array of matching satellite records

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "query": {
+      "description": "Search query that was executed",
+      "type": "string"
+    },
+    "satellites": {
+      "description": "Array of matching satellite records",
+      "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 matching satellites found",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "query",
+    "satellites"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "ISS"
+  },
+  {
+    "limit": 20,
+    "query": "Starlink"
+  }
+]

First observedApr 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's additional mention that it returns matching satellites with NORAD IDs and TLE data adds useful behavioral context. This goes beyond the schema annotations without contradicting them.

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?

The description is a single, front-loaded sentence with no redundant words. It efficiently communicates the core purpose and return value.

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 simple search tool, the description is quite complete: it states what is searched, what is returned, and the annotations cover safety. An output schema exists, and the description sufficiently explains return values. Minor gaps like pagination behavior are covered by the schema's limit parameter.

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%, so both parameters (query and limit) are already fully documented. The description adds no additional parameter-specific meaning beyond what the schema provides, meriting the baseline score.

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?

The description clearly states the tool searches for satellites by name or keyword, which is a specific verb+resource. It also distinguishes itself from sibling tools like get_tle by indicating it returns matching satellites with NORAD IDs and TLE data, implying search functionality rather than direct retrieval.

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 implies usage for finding satellites by name or keyword but does not explicitly state when to use this tool over alternatives. No exclusions or alternative tool references are provided, so the guidance is only implied.

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

All Tle tools Inspect

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.