Spacex

Get Starlink

get_starlink

Read-onlyIdempotent

Get live Starlink satellites from the public catalog (CelesTrak), sorted by most recent orbital-element epoch. Returns object name, NORAD/COSPAR id, epoch, mean motion, inclination, and eccentricity.

Input Schema

Name	Required	Description	Default
`limit`	No	Number of satellites to return (default 20, max 200)

Output Schema

Name	Required	Description
`total`	No
`source`	No
`_source`	No
`satellites`	No	Array of Starlink satellites
`_fetched_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedJul 2, 2026
- addedOutput schema / properties / _fetched_at
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / _source
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / satellites / items / properties / DECAY_DATE
```
Removed value: -{
-  "description": "Decay date if deorbited",
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- addedOutput schema / properties / satellites / items / properties / ECCENTRICITY
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / satellites / items / properties / EPOCH
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / satellites / items / properties / INCLINATION
```
Added value: +{
+  "type": "number"
+}
```
- removedOutput schema / properties / satellites / items / properties / LAUNCH_DATE
```
Removed value: -{
-  "description": "Launch date",
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- addedOutput schema / properties / satellites / items / properties / MEAN_MOTION
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / satellites / items / properties / NORAD_CAT_ID
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / satellites / items / properties / OBJECT_ID
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / satellites / items / properties / OBJECT_NAME / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```
- removedOutput schema / properties / satellites / items / required
```
Removed value: -[
-  "OBJECT_NAME",
-  "LAUNCH_DATE",
-  "DECAY_DATE"
-]
```
- addedOutput schema / properties / source
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / total
```
Added value: +{
+  "type": "number"
+}
```
- removedOutput schema / required
```
Removed value: -[
-  "satellites"
-]
```

Changed1 schema field changedJul 2, 2026

changedInput schema / properties / limit / description

Previous value: -"Number of satellites to return (default 20)"New value: +"Number of satellites to return (default 20, max 200)"

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "satellites": {
+      "description": "Array of Starlink satellites",
+      "items": {
+        "properties": {
+          "DECAY_DATE": {
+            "description": "Decay date if deorbited",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "LAUNCH_DATE": {
+            "description": "Launch date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "OBJECT_NAME": {
+            "description": "Satellite object name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "OBJECT_NAME",
+          "LAUNCH_DATE",
+          "DECAY_DATE"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "satellites"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {},
+  {
+    "limit": 50
+  }
+]
```
First observedApr 14, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds source, sorting, and return fields, which is useful but does not disclose potential limitations like pagination, rate limits, or refresh behavior. Given annotations cover the safety profile, this is adequate but not rich.

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 concise sentences: the first front-loads purpose and source, the second lists return fields. No unnecessary words or repetition of schema details.

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?

For a simple read-only tool with one optional parameter, annotations, and an output schema, the description is complete. It covers purpose, data source, sorting, and return fields, leaving no significant gaps for an agent to invoke correctly.

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% for the single optional `limit` parameter, including default and max values in the schema. The description does not mention `limit` at all, so it adds no parameter semantics beyond what the schema provides. Baseline 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?

Clearly states 'Get live Starlink satellites' with specific source (CelesTrak), sorting by epoch, and lists return fields. Unambiguously distinct from sibling tools like get_crew, get_rockets, and launch tools.

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 implies usage for live Starlink satellite data from the public catalog, which is clear context. However, it does not explicitly mention alternatives or exclusions, though no sibling tool overlaps with this purpose.

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

All Spacex 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.