Skip to main content
Glama
Bigred97

au-weather-mcp

air_quality

Get current air-quality readings for any Australian location. Check PM2.5, PM10, ozone, and AQI indices for health or bushfire smoke planning.

Instructions

Return current air-quality readings for any Australian location.

Sourced from Open-Meteo's air-quality API, which merges Copernicus CAMS European + global air-composition models. Returns PM2.5, PM10, ozone, nitrogen dioxide, sulphur dioxide, carbon monoxide (all µg/m³), plus the European and US AQI indices with plain-English labels.

Especially useful during AU bushfire season (Oct–Mar) when smoke can push PM2.5 above safe levels across whole regions.

Examples: # Current Sydney air quality resp = await air_quality("sydney") # resp.current.pm2_5_ugm3 == 8.8 # resp.current.european_aqi == 21 # resp.current.european_aqi_label == 'Good' # resp.current.us_aqi == 39 # resp.current.us_aqi_label == 'Good'

# Bushfire smoke check for the Blue Mountains
resp = await air_quality("-33.7,150.3")

# Brisbane CBD via postcode
resp = await air_quality("4000")

When to use: - "Is the air clean enough to go for a run in ?" - Bushfire smoke or burn-off impact checks - Asthma / allergy planning - Long-term air quality monitoring (call periodically and chart)

Returns: AirQualityResponse with current populated (pollutants + AQI scales), plus location metadata, source_url, attribution, and server_version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYesAny Australian location. Same accepted shapes as latest(): curated ID, place name, state code/name, postcode, or 'lat,lng' coordinates.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
staleNo
stateYes
sourceNoOpen-Meteo Air Quality (CAMS European + global merge)
currentNo
latitudeYes
timezoneYes
longitudeYes
source_urlYes
attributionNoWeather data by Open-Meteo.com (https://open-meteo.com), licensed under CC BY 4.0. Underlying data includes the Australian Bureau of Meteorology (https://www.bom.gov.au) under Open-Meteo's licensing arrangement.
location_idYes
retrieved_atYes
stale_reasonNo
location_nameYes
location_inputYes
server_versionYes
location_resolutionYes
Behavior5/5

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

With no annotations provided, the description fully discloses the data source (Open-Meteo, Copernicus CAMS), units (µg/m³), and output structure (pollutants, AQI scales, plain-English labels). It also notes seasonal relevance and coordinates. No contradictions.

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?

The description is well-structured with a clear opening, source note, examples, use cases, and return summary. It is concise without unnecessary repetition, and key information is front-loaded.

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?

Given the tool's simplicity (one parameter) and the presence of an output schema, the description is complete. It covers all aspects: purpose, usage, parameter, output, and context. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a single 'location' parameter. The description adds significant meaning beyond the schema by providing multiple examples (city names, postcodes, coordinates) and explaining that it accepts curated IDs, place names, states, and lat,lng. This enriches semantic understanding.

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 explicitly states it returns current air-quality readings for Australian locations, listing specific pollutants and AQI indices. It distinguishes from sibling tools like get_weather and compare_locations by focusing solely on air quality.

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 'When to use' section provides concrete examples such as checking air quality before running, during bushfire season, for asthma planning, and long-term monitoring. It lacks explicit 'when not to use' or alternatives, but the guidance is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bigred97/au-weather-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server