Skip to main content
Glama

BRAINIAC Space & Satellite Intelligence

Analyze launch-window weather

space-intelligence_launch-window-weather-analyze
Read-onlyIdempotent

Analyze caller-supplied weather samples or optional key-free Open-Meteo hourly forecasts against simple go/no-go thresholds. Price $0.04 USDC. POST /api/v1/space-intelligence/launch-window-weather-analyze. 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_launch-window-weather-analyze"
  }
}

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.
goCountNogoCount. Number.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
sampleCountNosampleCount. 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 declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds real behavioral context the annotations cannot: the $0.04 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms and does not execute — an agent needs this to interpret a no-result response.

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 short sentences, front-loaded with the capability, then the price/endpoint, then the payment-failure behavior. Nothing is padded, though the raw endpoint string is arguably redundant with the tool name.

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?

An output schema exists so return values need no explanation, and payment semantics are covered. However, all 17 parameters are optional, and the description never states what happens on an empty call, what default thresholds apply, or which inputs are mutually exclusive — meaningful gaps for a tool 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% and every one of the 17 properties is self-documented, so the baseline is 3. The description adds conceptual framing for the weather/openMeteo inputs and thresholds, but says nothing about the many other parameters (tles, observers, images, celestrak, horizonHours, stepMinutes), so it does not materially exceed the schema.

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 gives a specific verb and resource ('Analyze ... launch-window weather') and names the two accepted input modes (caller-supplied weather samples or Open-Meteo hourly forecasts) plus the output concept (go/no-go thresholds). That is enough to separate it from siblings like satellite-imagery-cloud-assess or satellite-pass-predict, though no sibling is named 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 through the input modes ('caller-supplied weather samples or optional key-free Open-Meteo hourly forecasts'), which tells an agent how to invoke it but not when to prefer it over cloud assessment or pass prediction. There are no exclusions and no explicit when-not 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