Skip to main content
Glama

BRAINIAC Space & Satellite Intelligence

Detect satellite orbit changes

space-intelligence_satellite-orbit-change-detect
Read-onlyIdempotent

Compare before/after TLE mean elements for inclination, RAAN, mean motion, and apogee/perigee deltas. Maneuver confirmation is not claimed. Price $0.04 USDC. POST /api/v1/space-intelligence/satellite-orbit-change-detect. 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-orbit-change-detect"
  }
}

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.
pairCountNopairCount. Number.
changeCountNochangeCount. Number.
limitationsNolimitations. Array.
orbitalModelNoorbitalModel. String.
apiKeyRequiredNoapiKeyRequired. Boolean.
celestrakFetchedNocelestrakFetched. Boolean.
openMeteoFetchedNoopenMeteoFetched. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
paidOrbitalApiUsedNopaidOrbitalApiUsed. Boolean.
commercialImageryUsedNocommercialImageryUsed. Boolean.
orbitalUncertaintyNoteNoorbitalUncertaintyNote. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing commercial and auth behavior: $0.04 USDC per call, the POST endpoint, and crucially that an unpaid call returns x402 payment terms without running. That payment-gate behavior is something readOnlyHint/openWorldHint cannot convey and materially changes how an agent must sequence the call.

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?

Four short sentences in a deliberate order: what is computed, what is not claimed, price, then endpoint/payment behavior. Every sentence carries distinct operational information and the purpose is front-loaded.

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?

For a tool with 17 parameters, many mutually substitutable input carriers (tles, celestrak, file, files, csv, json, text), a nested file object, and an output schema, the description omits which input form is expected or preferred. Safety and payment context are complete thanks to annotations plus the price/x402 disclosure, but the input-selection gap is significant at this complexity.

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 all 17 parameters (including the nested tle side enum of before/after and the celestrak/observers/openMeteo branches) are already documented. The description only implies that the 'tles' array is the relevant input via 'TLE mean elements' and adds no format or precedence guidance for the competing input channels, so baseline 3 applies.

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?

States a specific verb and resource: compare before/after TLE mean elements, and enumerates exactly which elements are compared (inclination, RAAN, mean motion, apogee/perigee deltas). The explicit scope limit 'Maneuver confirmation is not claimed' further pins down what this tool is and is not, distinguishing it from a maneuver-detection tool.

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?

Implicit usage is clear from the purpose, and the 'maneuver confirmation is not claimed' caveat tells the agent not to over-read results. However, no sibling alternative is named (e.g., object-catalog-compare or conjunction-screen) and no prerequisite is stated about which input channel to supply (tles vs celestrak vs file).

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