NASA MCP Server

JPL fireball events

jpl_fireball

Read-onlyIdempotent

Find fireball (bolide) events from US Government sensors via NASA JPL; filter by date, location, velocity, energy, impact.

Instructions

Fireball (bolide) events reported by US Government sensors, from the JPL Fireball API.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of events (1-1000).
`req_alt`	No	Only events with an altitude.
`req_loc`	No	Only events with a location.
`req_vel`	No	Only events with a velocity.
`vel_max`	No	Maximum velocity (km/s).
`vel_min`	No	Minimum velocity (km/s).
`date_max`	No	Latest event date (YYYY-MM-DD).
`date_min`	No	Earliest event date (YYYY-MM-DD).
`energy_max`	No	Maximum total radiated energy (1e10 J).
`energy_min`	No	Minimum total radiated energy (1e10 J).
`impact_e_max`	No	Maximum estimated impact energy (kt).
`impact_e_min`	No	Minimum estimated impact energy (kt).
`req_vel_comp`	No	Only events with velocity components.

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv1.2.0Oct 1, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / date_max / description

Previous value: -"End date (YYYY-MM-DD)"New value: +"Latest event date (YYYY-MM-DD)."

addedInput schema / properties / date_max / pattern

Added value: +"^(now|[+-]\\d{1,5}|\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}(:\\d{2})?)?)$"

changedInput schema / properties / date_min / description

Previous value: -"Start date (YYYY-MM-DD)"New value: +"Earliest event date (YYYY-MM-DD)."

addedInput schema / properties / date_min / pattern

Added value: +"^(now|[+-]\\d{1,5}|\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}(:\\d{2})?)?)$"

addedInput schema / properties / energy_max

Added value: +{
+  "description": "Maximum total radiated energy (1e10 J).",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / energy_min

Added value: +{
+  "description": "Minimum total radiated energy (1e10 J).",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / impact_e_max

Added value: +{
+  "description": "Maximum estimated impact energy (kt).",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / impact_e_min

Added value: +{
+  "description": "Minimum estimated impact energy (kt).",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / limit / default
```
Added value: +50
```

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results to return"New value: +"Maximum number of events (1-1000)."

addedInput schema / properties / limit / maximum
```
Added value: +1000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / req_alt

Added value: +{
+  "description": "Only events with an altitude.",
+  "type": "boolean"
+}

addedInput schema / properties / req_loc

Added value: +{
+  "description": "Only events with a location.",
+  "type": "boolean"
+}

addedInput schema / properties / req_vel

Added value: +{
+  "description": "Only events with a velocity.",
+  "type": "boolean"
+}

addedInput schema / properties / req_vel_comp

Added value: +{
+  "description": "Only events with velocity components.",
+  "type": "boolean"
+}

addedInput schema / properties / vel_max

Added value: +{
+  "description": "Maximum velocity (km/s).",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / vel_min

Added value: +{
+  "description": "Minimum velocity (km/s).",
+  "minimum": 0,
+  "type": "number"
+}

First observedAug 18, 2025

TDQS

B3.2/5.0

Behavior3/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 the data provenance (US Government sensors), which is useful context, but says nothing about return format, ordering, or pagination behavior for a 13-parameter query tool.

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?

A single efficient sentence with the resource and source front-loaded. Nothing is wasted, though it is arguably too short to be maximally useful.

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?

Annotations cover safety and the schema fully documents parameters, but for a tool with 13 filter parameters and no output schema the description never hints at the filtering/faceting capability an agent would need to know it can narrow results. Adequate but with a clear gap.

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% with all 13 parameters individually documented, so the schema does the heavy lifting. The description adds no additional meaning about filters, ranges, or the date/velocity/energy semantics beyond what the schema already states.

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 resource (fireball/bolide events) and names the data source (JPL Fireball API) and provenance (US Government sensors). It is clearly distinct from orbital-element siblings like jpl_sbdb or jpl_horizons, though the verb is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, and no mention of the rich filtering capability that would be the main reason to select it. The agent must infer usage entirely from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

JPL fireball events

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools