Skip to main content
Glama

get_space_telemetry

Live CelesTrak Starlink SATCAT satellite counts, Launch Library 2 orbital launch windows, and space/power equity quotes (RKLB, ASTS, LUNR, PL, BE, CEG, TLN). $0.05.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_space_telemetry"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With zero annotations the description carries the full burden, and it does disclose two behavioral facts the schema cannot: the data is 'Live' and upstream-sourced, and the call costs $0.05. It does not cover response size, refresh/caching behavior, error modes, or payload shape for a three-source bundle.

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

Conciseness4/5

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

A single sentence with no filler, and the data sources are front-loaded. The ticker parenthetical is slightly cryptic without saying why those specific space/power names are grouped, but it is information rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description usefully enumerates the three data categories as a proxy for return content, which is the strongest part of the definition. It still leaves the response format, units, and freshness cadence unspecified for what is effectively a three-source aggregate call.

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

Parameters4/5

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

The tool takes no parameters, so there is no parameter semantics to document and the baseline of 4 applies. Nothing in the description misrepresents the empty input schema.

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 names the concrete resources delivered: CelesTrak Starlink SATCAT satellite counts, Launch Library 2 orbital launch windows, and quotes for a specific ticker list. That is specific enough to distinguish it from get_stock_quote, which covers single-equity quotes. It lacks an explicit verb ('returns'/'fetches'), so the operation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use context, no exclusions, and no mention of when an agent should prefer get_stock_quote over this bundle. The only guidance-adjacent text is the ticker parenthetical and the price, neither of which tells the agent when to invoke it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources