Skip to main content
Glama

jpl_fireball

Retrieve NASA JPL fireball data to track atmospheric impact events by date range, enabling analysis of meteoroid entries and energy releases.

Instructions

Fireball data - atmospheric impact events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return
date_minNoStart date (YYYY-MM-DD)
date_maxNoEnd date (YYYY-MM-DD)

Implementation Reference

  • Core handler function that executes the jpl_fireball tool logic: transforms params, calls JPL Fireball API, formats response.
    export async function jplFireballHandler(params: FireballParams) {
      try {
        // Construct the Fireball API URL
        const url = 'https://ssd-api.jpl.nasa.gov/fireball.api';
        
        // Transform parameter names from underscore to hyphenated format
        const transformedParams = transformParamsToHyphenated(params);
        
        // Make the request to the Fireball API
        const response = await axios.get(url, { params: transformedParams });
        
        return {
          content: [
            {
              type: "text",
              text: `Retrieved ${response.data.count || 0} fireball events.`
            },
            {
              type: "text",
              text: JSON.stringify(response.data, null, 2)
            }
          ],
          isError: false
        };
      } catch (error: any) {
        console.error('Error in JPL Fireball handler:', error);
        
        return {
          isError: true,
          content: [{
            type: "text",
            text: `Error: ${error.message || 'An unexpected error occurred'}`
          }]
        };
      }
    } 
  • Zod schema for validating input parameters to the jpl_fireball tool.
    export const fireballParamsSchema = z.object({
      date_min: z.string().optional(),
      date_max: z.string().optional(),
      energy_min: z.number().optional(),
      energy_max: z.number().optional(),
      impact_e_min: z.number().optional(),
      impact_e_max: z.number().optional(),
      vel_min: z.number().optional(),
      vel_max: z.number().optional(),
      alt_min: z.number().optional(),
      alt_max: z.number().optional(),
      req_loc: z.boolean().optional().default(false),
      req_alt: z.boolean().optional().default(false),
      req_vel: z.boolean().optional().default(false),
      req_vel_comp: z.boolean().optional().default(false),
      req_impact_e: z.boolean().optional().default(false),
      req_energy: z.boolean().optional().default(false),
      limit: z.number().optional().default(50)
    });
  • src/index.ts:508-511 (registration)
    Tool registration in tools/manifest response, declaring the jpl_fireball tool.
      name: "jpl_fireball",
      id: "jpl/fireball",
      description: "Fireball atmospheric impact data reported by US Government sensors"
    },
  • src/index.ts:1050-1069 (registration)
    Detailed tool registration including input schema in tools/list response.
      name: "jpl_fireball",
      description: "Fireball data - atmospheric impact events",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Maximum number of results to return"
          },
          "date_min": {
            type: "string", 
            description: "Start date (YYYY-MM-DD)"
          },
          "date_max": {
            type: "string",
            description: "End date (YYYY-MM-DD)"
          }
        }
      }
    },
  • Import of helper utility used to transform underscore params to hyphenated for API compatibility.
    import { transformParamsToHyphenated } from '../../utils/param-transformer';
    
    // Schema for validating JPL Fireball request parameters
    export const fireballParamsSchema = z.object({
      date_min: z.string().optional(),
      date_max: z.string().optional(),
      energy_min: z.number().optional(),
      energy_max: z.number().optional(),
      impact_e_min: z.number().optional(),
      impact_e_max: z.number().optional(),
      vel_min: z.number().optional(),
      vel_max: z.number().optional(),
      alt_min: z.number().optional(),
      alt_max: z.number().optional(),
      req_loc: z.boolean().optional().default(false),
      req_alt: z.boolean().optional().default(false),
      req_vel: z.boolean().optional().default(false),
      req_vel_comp: z.boolean().optional().default(false),
      req_impact_e: z.boolean().optional().default(false),
      req_energy: z.boolean().optional().default(false),
      limit: z.number().optional().default(50)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what data is retrieved without mentioning any behavioral traits such as rate limits, authentication needs, data freshness, or response format. For a data retrieval tool with zero annotation coverage, this leaves significant gaps in understanding how it operates.

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?

The description is very concise with a single phrase, 'Fireball data - atmospheric impact events', which efficiently conveys the core purpose. It's front-loaded and wastes no words, though it could benefit from slightly more detail to improve clarity without sacrificing brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a data retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the returned data looks like, any limitations (e.g., date ranges, data sources), or how it integrates with sibling tools. This leaves the agent with insufficient context to use the tool effectively beyond basic parameter input.

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?

The input schema has 100% description coverage, with clear documentation for all three parameters (limit, date_min, date_max). The description adds no additional meaning beyond what the schema provides, such as default values or usage examples. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 clearly states the tool's purpose as retrieving 'fireball data - atmospheric impact events', which is specific about the resource (fireball data) and domain (atmospheric impact events). However, it doesn't distinguish this tool from its siblings (like nasa_neo or nasa_donki which might also handle space-related events), so it doesn't fully differentiate from alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any specific context, prerequisites, or exclusions, and with multiple sibling tools available (e.g., nasa_neo for near-Earth objects, nasa_donki for space weather), there's no indication of how this tool fits into the broader set.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ProgramComputer/NASA-MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server