Skip to main content
Glama
WildFireBot MCP Server

WildFireBot MCP Server

by nycbagel

pm25_to_aqi

Convert a PM2.5 concentration in µg/m³ to a US EPA 2024 AQI value with category, using the official breakpoint equation. Returns the AQI plus a non-health-advisory disclaimer.

Instructions

Convert one PM2.5 concentration in micrograms per cubic meter to the US EPA 2024 AQI with the breakpoint equation. Does not compute a 24-hour average or a NowCast. The result includes the AQI, the category, and a disclaimer that this is not a health advisory.

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": {
      "concentration": "<concentration>"
    },
    "name": "pm25_to_aqi"
  }
}

Input Schema

NameRequiredDescriptionDefault
concentrationYesPM2.5 concentration in micrograms per cubic meter

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 discloses the algorithm (EPA 2024 breakpoint equation), the input granularity (single concentration, not an average), and the return payload (AQI, category, non-advisory disclaimer). It never explicitly says the operation is stateless and side-effect free, which would have closed the remaining gap for a tool with zero annotation coverage.

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?

Three short sentences: the core action first, the scope exclusions second, the return shape last. Nothing is redundant with the title or the schema, and no sentence could be dropped without losing information.

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 one-parameter pure conversion with an output schema already present, the description covers everything an agent needs: the standard used, the equation family, the excluded aggregation modes, and the fact that the output includes a non-advisory disclaimer. Nothing required for correct invocation is missing.

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% and the single parameter already documents its unit and minimum, so the schema does the heavy lifting. The description reinforces the cardinality ('one PM2.5 concentration') but adds no format, rounding, or range detail beyond the schema — the baseline 3.

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 states a specific verb and resource ('Convert one PM2.5 concentration in micrograms per cubic meter to the US EPA 2024 AQI') and names the exact method (breakpoint equation) and version year. It also scopes out what it does not do (24-hour average, NowCast), which separates it from the forecast-oriented siblings that produce multi-hour aggregates.

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?

The exclusions ('Does not compute a 24-hour average or a NowCast') tell an agent when this tool is the wrong choice, which is real usage guidance. It stops short of naming an alternative for those cases, so the agent must infer the handoff rather than being routed explicitly.

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