Skip to main content
Glama

Firms Hotspots Near

firms_hotspots_near
Read-onlyIdempotent

"Are there any fires near Boulder, Colorado?" / "active fire detections within 50 km of this point", NASA FIRMS satellite hotspot detections around a latitude/longitude, sorted nearest first with the distance in km. Same measured detections as firms_hotspots_area, addressed the way a question about a place is actually asked. Returns distance_km, position, acquisition time, brightness temperature, fire radiative power and confidence.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": 40.015,
      "longitude": -105.27,
      "radius_km": 100
    },
    "name": "firms_hotspots_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoStart date YYYY-MM-DD. Omit for the most recent data.
limitNoMax detections to return (default 100, max 1000).
sourceNoSatellite product. "VIIRS_SNPP_NRT" (default, 375 m, global, near-real-time), "VIIRS_NOAA20_NRT", "VIIRS_NOAA21_NRT", "MODIS_NRT" (1 km, longest record), "LANDSAT_NRT" (30 m, US/Canada only), or the "_SP" standard-processing variants for the quality-controlled archive.
_apiKeyNoYour FIRMS MAP_KEY. Free at https://firms.modaps.eosdis.nasa.gov/api/map_key/
latitudeYesLatitude in decimal degrees, -90 to 90.
day_rangeNoNumber of days to search, 1-5 (default 1).
longitudeYesLongitude in decimal degrees, -180 to 180.
radius_kmNoSearch radius in km (default 100, max 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: results are sorted nearest first, distance is reported in km, and it enumerates the returned fields (distance_km, position, acquisition time, brightness temperature, FRP, confidence), plus notes the detections are the same measured set as firms_hotspots_area — implying no double counting. Rate limits and error behavior are not covered.

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 dense paragraph with no filler, and the sibling contrast plus return fields are all load-bearing. Minor weakness: it opens with two quoted user questions rather than a direct statement of purpose, delaying the front-loaded answer slightly.

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

Completeness4/5

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

For an 8-parameter read-only tool with full schema coverage and no output schema, the definition supplies purpose, spatial framing, sort order and a summary of returned fields — enough to invoke correctly. Remaining minor gaps (pagination via limit, result-empty behavior) are handled by the schema or are low-risk for a read-only query.

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%, so every parameter including source variants, day_range limits and radius caps is already documented in structured form. The description only implies radius filtering through the '50 km' example and adds no syntax or defaults beyond the schema, so baseline 3 applies.

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?

The description names a specific resource (NASA FIRMS satellite hotspot detections) and the specific addressing scheme (around a latitude/longitude), and explicitly distinguishes itself from firms_hotspots_area as the point-addressed variant of the same detections. An agent can route between the two siblings from the description alone.

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

Usage Guidelines4/5

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

Two concrete example queries ('Are there any fires near Boulder' and 'active fire detections within 50 km of this point') establish the use case, and the explicit contrast with firms_hotspots_area gives an alternative for area-based questions. It stops short of stating exclusions, such as when to use the area or archive tools instead.

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.