Skip to main content
Glama

BRAINIAC Space & Satellite Intelligence

Check satellite image quality

space-intelligence_satellite-image-quality-check
Read-onlyIdempotent

Score caller-supplied sharpness, SNR, resolution, and cloud metrics for EO scenes. Missing metrics are not invented. Price $0.03 USDC. POST /api/v1/space-intelligence/satellite-image-quality-check. 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-image-quality-check"
  }
}

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.
sceneCountNosceneCount. 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 readOnly/idempotent/non-destructive, but the description adds material context those fields cannot: a $0.03 USDC cost, the x402 payment handshake, and the fact that an unpaid call returns payment terms and does not execute. The "missing metrics are not invented" guarantee is a useful non-hallucination contract. It does not state rate limits or what the score output looks like, but the output schema covers returns.

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 purpose before pricing and transport details, with no filler. The literal endpoint path and price duplicate information an agent may not need at decision time, but the ordering keeps the call-relevant facts first.

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 output schema and annotations cover returns and safety, and payment behavior is disclosed, so core needs are met. However, for a 17-parameter schema with nested objects that includes tles, weather, observers, celestrak, and openMeteo, the description gives no hint that the images array is the actual input surface, leaving the agent to work this out from the schema alone.

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 four metrics are already documented per-field; the description echoes them without adding formats, units, acceptable ranges, or guidance on which of the 17 top-level parameters matter. Baseline 3 applies when the schema carries the loading, but the description does nothing to help an agent ignore the many unrelated orbital/weather parameters.

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 ("Score") and enumerates the metrics scored (sharpness, SNR, resolution, cloud) against EO scenes, which lets an agent distinguish this from siblings like satellite-imagery-cloud-assess. It stops short of naming that sibling or stating what this tool does not cover, so the differentiation is inferred from the metric list rather than explicit.

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?

"caller-supplied" implies the agent must already hold metrics rather than expect the tool to fetch them, and "Missing metrics are not invented" signals acceptable partial input. There is no explicit statement of when to choose this over space-intelligence_satellite-imagery-cloud-assess or what to do when no metrics are available at all, leaving the routing decision to inference.

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