Skip to main content
Glama

BRAINIAC Space & Satellite Intelligence

Screen satellite conjunctions

space-intelligence_satellite-conjunction-screen
Read-onlyIdempotent

Screen approximate miss distances between caller-supplied TLEs over a horizon. Not a covariance-based conjunction assessment. Price $0.05 USDC. POST /api/v1/space-intelligence/satellite-conjunction-screen. 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-conjunction-screen"
  }
}

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.
limitationsNolimitations. Array.
orbitalModelNoorbitalModel. String.
screenedCountNoscreenedCount. Number.
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
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive semantics, and the description adds genuinely new behavior: a $0.05 USDC price and an x402 payment gate where an unpaid call returns payment terms instead of results. That gating detail materially changes how an agent should interpret a response. It says nothing about output shape, but an output schema exists to cover that.

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, each carrying distinct information: capability, scope limitation, price, endpoint, and payment-gate behavior. The capability statement and the exclusion are front-loaded with no filler.

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?

The description covers the payment gate and the core input concept, which are the two highest-risk unknowns. However, for a 17-parameter tool with nested objects, it gives no help deciding among the many optional input groups, and the schema's own descriptions are purely structural ('csv, string, length 0 to 200000'). An agent can call the tool but cannot tell which of the sibling-shaped payload groups are actually meaningful here.

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%, so the baseline is 3. The description implies the relevant inputs are TLE entries and a time horizon (mapping to the tles and horizonHours properties), but it adds no format or validity detail, and says nothing about the many other input groups (csv, file, images, weather, celestrak, openMeteo, observers, catalogObjects) that appear in the schema.

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: 'Screen approximate miss distances between caller-supplied TLEs over a horizon.' It also draws an explicit boundary against a different class of analysis ('Not a covariance-based conjunction assessment'), which lets an agent distinguish it from siblings like satellite-pass-predict or orbit-change-detect.

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 'caller-supplied TLEs' phrasing and the exclusion of covariance-based assessment make the applicable context clear, and the payment note tells the agent the first call may not execute. It does not name a specific sibling alternative for the excluded case, so it stops short of full routing guidance.

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