Skip to main content
Glama
WildFireBot MCP Server

WildFireBot MCP Server

by nycbagel

forecast_smoke_aqi

Estimate PM2.5 and US EPA AQI at a latitude and longitude by combining NASA FIRMS fire detections, wind forecasts, and background air quality for smoke screening.

Instructions

Forecast PM2.5 and the US EPA AQI at one latitude and longitude. Adds a Gaussian plume from each NASA FIRMS fire cluster, using fire radiative power and the Open-Meteo wind forecast, on top of Open-Meteo's background PM2.5. Works for a new fire because it does not need a history of observations. Returns horizons, degraded-mode notices, and a disclaimer. This is a screening estimate, not an official AQI and not a health advisory. Missing FIRMS_MAP_KEY, AIRNOW_API_KEY, or OPENAQ_API_KEY is reported in notices.

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_aqi"
  }
}

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
radius_kmNoFire search radius in kilometers
stabilityNoPasquill-Gifford stability class A through FD
plume_height_mNoAssumed plume height in meters
emission_factorNoPM2.5 emission in grams per second per MW of FRP

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 substantial work: it explains the modeling method, that degraded-mode notices and a disclaimer are returned, and that a missing FIRMS_MAP_KEY, AIRNOW_API_KEY, or OPENAQ_API_KEY surfaces as a notice rather than a hard failure. It also sets accuracy expectations ('screening estimate, not an official AQI'). It stops short of stating latency, rate limits, or what triggers degraded mode.

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?

Five tight sentences, front-loaded with what is forecast, then method, then the caveats that matter for interpretation. Every sentence carries operational value, including the API-key notice sentence. Minor density of domain jargon (FRP, Pasquill-Gifford) but nothing is wasted.

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?

Seven parameters are fully described in the schema and an output schema exists, so the description need not enumerate return fields; it still flags horizons, degraded-mode notices, and the disclaimer, which is useful. Method and caveats are covered. The only real gap is sibling differentiation, which leaves a routing ambiguity for an agent choosing between forecast tools.

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 all seven parameters (including units and the Pasquill-Gifford stability class) are already documented in the schema. The description adds only the notion of a single lat/lon target and the implicit link between FIRMS detections and the fire-search parameters, which is marginal beyond the schema. Baseline 3 is appropriate.

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 verb and resource with scope: forecasting PM2.5 and US EPA AQI at one latitude/longitude, and describes the modeling approach (Gaussian plume from FIRMS clusters plus Open-Meteo background). It is clear about what it produces, but never distinguishes itself from the sibling 'forecast_smoke', leaving the agent to guess which forecast variant to pick.

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?

Offers an implicit when-to-use cue: 'Works for a new fire because it does not need a history of observations,' which tells the agent this is the right choice for fresh ignitions. It also warns the output is a screening estimate rather than an official AQI or health advisory. However, it names no alternatives and gives no explicit when-not-to-use condition, so routing against 'forecast_smoke' and 'pm25_to_aqi' remains inferred.

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