Skip to main content
Glama

firms_active_area

Query NASA FIRMS for active fire detections within a geographic bounding box using VIIRS or MODIS sensors. Returns fire hotspots with brightness, confidence, and fire radiative power.

Instructions

Query NASA FIRMS for active fire detections within a geographic bounding box. Returns fire hotspots with brightness, confidence, fire radiative power (FRP), and acquisition time. Supports VIIRS (375m) and MODIS (1km) sensors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days to query (1, 2, or 7). Default: 1
eastYesEastern longitude of the bounding box (-180 to 180)
westYesWestern longitude of the bounding box (-180 to 180)
northYesNorthern latitude of the bounding box (-90 to 90)
southYesSouthern latitude of the bounding box (-90 to 90)
sourceNoFire detection satellite source. VIIRS_SNPP (Suomi NPP, 375m), VIIRS_NOAA20 (NOAA-20, 375m), or MODIS_NRT (Aqua/Terra, 1km). Default: VIIRS_SNPPVIIRS_SNPP
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions returned fields and sensors but omits details like pagination, rate limits, data freshness, or the read-only nature. It does not contradict any annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences deliver the core purpose and key details without extraneous information. Every sentence adds value.

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?

For a tool with six parameters and no output schema, the description covers basic functionality but lacks details on result limits, bounding box constraints, or ordering. Adequate but not comprehensive.

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 baseline is 3. The description adds context about sensor resolutions (375m vs 1km) and enumerates returned fields, but does not provide additional semantics for coordinates or days beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool queries NASA FIRMS for active fire detections within a bounding box, specifying the returned fields (brightness, confidence, FRP, acquisition time) and supported sensors (VIIRS, MODIS). This distinguishes it from sibling tools like firms_active_country or firms_active_point.

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?

The description implies use for area-based queries via bounding box but does not explicitly mention when to use alternatives like firms_active_point or firms_active_country. Sensor selection guidance is provided, but no when-not-to-use advice.

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/badchars/satellite-mcp'

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