Tle

Get Tle

get_tle

Read-onlyIdempotent

Fetch the Two-Line Element (TLE) set for a specific satellite by its NORAD catalog ID. Returns the satellite name, epoch date, and both TLE lines.

Input Schema

Name	Required	Description	Default
`norad_id`	Yes	NORAD catalog number for the satellite (e.g. 25544 for the ISS, 20580 for Hubble Space Telescope).

Output Schema

Name	Required	Description
`name`	Yes	Name of the satellite
`epoch`	Yes	Epoch date of the TLE set
`line1`	Yes	First line of the Two-Line Element set
`line2`	Yes	Second line of the Two-Line Element set
`norad_id`	Yes	NORAD catalog ID of the satellite

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "norad_id": 25544
+  },
+  {
+    "norad_id": 20580
+  }
+]

First observedApr 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral detail about the response structure (satellite name, epoch, TLE lines) beyond those annotations. No contradictions found.

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 two sentences, front-loaded with the action verb and resource, and contains no redundant information. Every sentence adds value.

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?

The tool is simple with one parameter, an output schema exists, and annotations cover safety. The description fully explains the purpose and what is returned, with no significant gaps for the agent to proceed.

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 coverage is 100% with a detailed description and examples for norad_id. The tool description does not add any parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 uses the specific verb 'Fetch' with the resource 'Two-Line Element (TLE) set', clearly scoping by NORAD catalog ID. It also lists the return fields (satellite name, epoch date, TLE lines), which further distinguishes it from sibling search_satellites.

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 when a NORAD ID is known, but it does not explicitly state alternatives or when not to use this tool (e.g., use search_satellites when the ID is unknown). No explicit prerequisites or exclusions are given.

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.