Skip to main content
Glama

BRAINIAC Space & Satellite Intelligence

Detect earth-observation changes

space-intelligence_earth-observation-change-detect
Read-onlyIdempotent

Compare before/after caller-supplied EO scene metadata (NDVI, brightness, cloud cover). Commercial imagery pixels are not downloaded. Price $0.04 USDC. POST /api/v1/space-intelligence/earth-observation-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_earth-observation-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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely non-redundant behavior: a $0.04 USDC price, the x402 payment gate, and the fact that an unpaid call returns payment terms without executing. That payment-gating disclosure is exactly the kind of context annotations cannot convey.

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?

Four short sentences, front-loaded with the core comparison and the pixel caveat before the commercial details. The endpoint URL is marginally useful for debugging but is the least valuable sentence; otherwise there is 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?

With 17 optional nested parameters and no required fields, the definition does not explain which input channel to use or how to express a before/after pair (the side enum values before/after/left/right/a/b carry that load). The output schema exists, so return values need no explanation, and payment behavior is covered, but the input-structuring gap keeps this at a minimum-viable 3 for a schema this complex.

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 the baseline is 3, and the schema descriptions are largely mechanical type/length restatements. The description adds only that NDVI, brightness, and cloud cover matter (fields inside the images array), and says nothing about how the 17 top-level inputs (csv, json, text, file, files, images, tles, weather, observers, openMeteo, etc.) relate or which to populate. Baseline 3 is appropriate.

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 verb and resource: 'Compare before/after caller-supplied EO scene metadata (NDVI, brightness, cloud cover).' It also draws a scope boundary that separates it from sibling tools by stating that imagery pixels are not downloaded, making it clearly a metadata-level analysis rather than an image-quality or cloud-assessment tool. It stops short of naming any sibling explicitly.

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 implied rather than stated: 'caller-supplied' and 'commercial imagery pixels are not downloaded' tell the agent this tool fits when metadata is already in hand, but there is no explicit when-to-use, when-not-to-use, or routing to alternatives like satellite-imagery-cloud-assess or satellite-image-quality-check. An agent must infer the selection criteria.

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