Skip to main content
Glama

get_air_quality

Read-onlyIdempotent

Retrieve hourly air quality forecasts for any coordinates: US EPA AQI with PM2.5, PM10, ozone and NO2 concentrations for the next 1 to 48 hours.

Instructions

Hourly air quality (up to 48 hours): US EPA AQI plus PM2.5, PM10, ozone and NO2 concentrations.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_air_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoNumber of hours to return (1-48).
latitudeYesLatitude in decimal degrees (-90 to 90).
longitudeYesLongitude in decimal degrees (-180 to 180).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the useful behavioral fact that coverage is capped at 48 hours, but says nothing about units, data source latency, or failure behavior for out-of-coverage coordinates.

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 front-loaded sentence that leads with the resource and time granularity before listing the measurements. Nothing is redundant or padded.

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 a read-only lookup with a fully documented schema, rich annotations and an output schema, the description covers what is needed to call it correctly. Minor gap: units for the pollutant concentrations are not stated, though they may live in the output schema.

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%, with descriptions for hours, latitude and longitude including ranges and defaults, so the baseline is 3. The description only reinforces the 48-hour ceiling already stated in the schema and adds no new semantics.

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?

Names a specific resource (hourly air quality) and enumerates exactly what is returned: US EPA AQI plus PM2.5, PM10, ozone and NO2. That content signature clearly separates it from the weather siblings, though the verb is implied rather than stated.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites, and does not point to any alternative (e.g. historical air quality or weather forecast tools). The only usage constraint, 'up to 48 hours', is a capability statement rather than guidance.

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