Skip to main content
Glama

BRAINIAC Space & Satellite Intelligence

Assess satellite imagery cloud cover

space-intelligence_satellite-imagery-cloud-assess
Read-onlyIdempotent

Classify caller-supplied cloud-cover percentages for EO scenes. Commercial imagery archives are not queried. Price $0.03 USDC. POST /api/v1/space-intelligence/satellite-imagery-cloud-assess. 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-imagery-cloud-assess"
  }
}

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.
sceneCountNosceneCount. Number.
limitationsNolimitations. Array.
usableCountNousableCount. Number.
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 cover read-only, idempotent, non-destructive and open-world, so the description's value-add is the payment behavior: $0.03 USDC, x402 terms returned on unpaid calls, and the guarantee that an unpaid call does not execute. That is real operational context an agent cannot get from the annotations.

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 and scope before the price and endpoint. The endpoint URL is arguably filler for an agent, but nothing is redundant or buried.

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?

Return values are covered by the output schema and payment is explained, so the core is complete. However, for a tool with 17 optional nested parameters, the description does not indicate which inputs actually drive the classification, leaving the agent to infer relevance from mechanical schema descriptions.

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, and the description adds nothing about parameters. Notably it never points to where the cloud-cover percentages belong (e.g., images[].cloudCoverPct) among 17 loosely related inputs such as tles, celestrak, observers and weather — a missed opportunity for a schema this broad.

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 and resource: "Classify caller-supplied cloud-cover percentages for EO scenes." The negative scoping line ("Commercial imagery archives are not queried") separates it from retrieval-style siblings without naming one, so an agent can tell what it does and what it does not do.

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" plus "archives are not queried" tells the agent it must bring its own data and cannot use this to fetch imagery. No sibling is named as an alternative and no prerequisites (e.g., when to prefer image-quality-check) are given.

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