Skip to main content
Glama
WildFireBot MCP Server

WildFireBot MCP Server

by nycbagel

forecast_smoke

Estimates relative wildfire smoke exposure at a latitude and longitude from NASA FIRMS fire detections and wind forecasts, returning hourly exposure scores plus nearby fires and PM2.5 data.

Instructions

Estimate relative wildfire smoke exposure at one latitude and longitude from NASA FIRMS fire detections and an Open-Meteo wind forecast. Returns nearby fire clusters, a wind summary, an hourly smoke-exposure score, nearby PM2.5 readings when monitors respond, degraded-mode notices, and a disclaimer. The score is a relative exposure index, not an official AQI and not a health advisory. Reads FIRMS_MAP_KEY, AIRNOW_API_KEY, and OPENAQ_API_KEY from the environment. A missing key is named in notices; the server keeps running.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "forecast_smoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesTarget latitude in decimal degrees (-90 to 90)
lonYesTarget longitude in decimal degrees (-180 to 180)
daysNoDays of FIRMS detections to read
hoursNoForecast length in hours
radius_kmNoFire search radius in kilometers
lookback_hoursNoHours to walk the back-trajectory

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned components, discloses required environment keys (FIRMS_MAP_KEY, AIRNOW_API_KEY, OPENAQ_API_KEY), and explains degraded-mode behavior when a key is missing ('the server keeps running'). It does not mention latency, caching, or rate limits, which keeps it short of a 5.

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?

Front-loaded with the core action, then outputs, then the AQI caveat, then environment requirements — a logical order with no filler. The return-value enumeration is long but each item is substantive; the only mild redundancy is listing outputs when an output schema already exists.

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

Completeness5/5

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

For a six-parameter, multi-source forecast tool with no annotations, the description covers inputs, outputs, credential requirements, failure/degraded behavior, and the interpretive limits of the score. An agent has everything needed to call it and to set expectations about the result.

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 the schema already documents lat, lon, days, hours, radius_km, and lookback_hours with ranges and defaults. The description adds only loose framing ('one latitude and longitude', 'nearby fire clusters') and no syntax or interpretation beyond the schema, so the 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?

States a specific verb and resource: 'Estimate relative wildfire smoke exposure at one latitude and longitude' from named sources (NASA FIRMS detections, Open-Meteo wind forecast). It also draws a boundary against the AQI-oriented sibling by declaring the score is 'a relative exposure index, not an official AQI and not a health advisory.'

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 when this tool is appropriate (relative exposure, not official AQI) but never explicitly routes the agent to forecast_smoke_aqi or pm25_to_aqi, nor states when not to use it. Usage is inferable rather than prescribed.

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

Deploy Server

Other Tools