Skip to main content
Glama

BRAINIAC Space & Satellite Intelligence

Build satellite observation evidence report

space-intelligence_satellite-observation-evidence-report
Read-onlyIdempotent

Aggregate passes, orbit changes, conjunctions, EO change, cloud/quality/license checks, launch weather, and catalog comparison with orbital uncertainty and TLE freshness notes. Price $0.08 USDC. POST /api/v1/space-intelligence/satellite-observation-evidence-report. 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-observation-evidence-report"
  }
}

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
asOfNoasOf. String.
statusNostatus. String.
findingsNofindings. Array.
sectionsNosections. Object.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
orbitalModelNoorbitalModel. String.
dataFreshnessNodataFreshness. Object.
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

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, but the description adds genuinely non-obvious context: a fixed $0.08 USDC price, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms and does not execute. That payment-gating disclosure is the kind of detail annotations cannot convey; only error/retry behavior and input sufficiency guidance are left out.

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?

Three sentences, front-loaded with the capability and followed by cost/transport and the payment failure mode. The long enumeration of domains is dense but each item corresponds to real report content, so it earns its space.

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

Completeness4/5

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

For a 17-parameter, nested-object tool with an output schema and full annotations, the description covers purpose, cost, transport, and payment gating adequately. The notable gap is that all parameters are optional, so the description never indicates what a minimal or meaningful invocation looks like or what happens with an empty payload.

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% across all 17 parameters and nested objects, so the schema already carries the semantics. The description adds no parameter-level meaning beyond naming the evidence domains, which is the expected baseline-3 outcome when the schema does the heavy lifting.

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 a specific aggregation action and enumerates the concrete evidence domains it covers (passes, orbit changes, conjunctions, EO change, cloud/quality/license checks, launch weather, catalog comparison), which maps closely onto the sibling tools. It stops short of explicitly saying it is the composite alternative to those individual tools, so an agent must infer that routing.

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?

Usage is only implied: by listing every sibling domain, the description suggests this is the one-shot bundle to call when a full evidence report is wanted. There is no explicit when-to-use/when-not statement and no mention of the individual tools as the narrower alternative.

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