Skip to main content
Glama

BRAINIAC Space & Satellite Intelligence

Predict satellite passes

space-intelligence_satellite-pass-predict
Read-onlyIdempotent

Predict approximate satellite passes over caller-supplied observers from TLEs (or optional key-free CelesTrak GP). Uses simplified Keplerian propagation; communicate orbital uncertainty and TLE freshness. Price $0.05 USDC. POST /api/v1/space-intelligence/satellite-pass-predict. An unpaid call returns the x402 payment terms and does not run.

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": "space-intelligence_satellite-pass-predict"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
tlesNotles, array. Optional.
filesNofiles, array. Optional.
imagesNoimages, array. Optional.
weatherNoweather, array. Optional.
celestrakNocelestrak, object. Optional.
observersNoobservers, array. Optional.
openMeteoNoopenMeteo, object. Optional.
stepMinutesNostepMinutes, number, from 0.5 to 60. Optional.
horizonHoursNohorizonHours, number, from 1 to 168. Optional.
catalogObjectsNocatalogObjects, array. Optional.
minElevationDegNominElevationDeg, number, from 0 to 90. Optional.
conjunctionThresholdKmNoconjunctionThresholdKm, number, from 0.1 to 10000. Optional.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
passCountNopassCount. Number.
limitationsNolimitations. Array.
horizonHoursNohorizonHours. Number.
orbitalModelNoorbitalModel. String.
observerCountNoobserverCount. Number.
apiKeyRequiredNoapiKeyRequired. Boolean.
satelliteCountNosatelliteCount. Number.
minElevationDegNominElevationDeg. Number.
celestrakFetchedNocelestrakFetched. Boolean.
openMeteoFetchedNoopenMeteoFetched. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
paidOrbitalApiUsedNopaidOrbitalApiUsed. Boolean.
commercialImageryUsedNocommercialImageryUsed. Boolean.
orbitalUncertaintyNoteNoorbitalUncertaintyNote. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, open-world, non-destructive), it discloses the pricing model ($0.05 USDC), the x402 paywall behavior on unpaid calls, and the accuracy limitation of simplified Keplerian propagation. These are exactly the traits that change how an agent budgets, authenticates, and reports results.

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?

Dense but front-loaded: purpose first, then data sources, caveats, price, and endpoint. The raw path/POST clause and price are terse telegraphic inserts rather than integrated prose, but no sentence is wasted.

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?

An output schema exists, so return values need not be described, and the paywall behavior is covered. However, for a 17-parameter tool with zero required parameters, the description never clarifies which combinations constitute a valid call (observers required, plus tles or celestrak), which is the most consequential gap.

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%, but the schema descriptions are generic type/length restatements, so the baseline of 3 applies. The description adds meaning only for observers, tles, and celestrak, leaving tuning parameters like stepMinutes, horizonHours, minElevationDeg, and conjunctionThresholdKm entirely uninterpreted.

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?

States a specific verb and resource: predicting approximate satellite passes over caller-supplied observers, sourced from TLEs or optional CelesTrak GP. That is clearly distinguishable from siblings like conjunction screening or orbit-change detection, though no sibling is named explicitly to route the agent.

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?

Gives implicit guidance by naming the data sources (TLEs vs key-free CelesTrak GP) and warning to communicate uncertainty and TLE freshness. It never says when to prefer this tool over conjunction-screen or observation-evidence-report, and gives no preconditions for a valid request (e.g., observers plus a source).

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