API Hub MCP — 337+ Tools

get_air_quality

Retrieve current air quality data including European AQI, US AQI, PM2.5, PM10, and ozone levels for any city. Simply provide the city name to get real-time pollution measurements.

Instructions

Get current air quality data for any city.

Uses Open-Meteo Air Quality API (free, no key) after geocoding the city.
Returns European AQI, US AQI, PM2.5, PM10, and ozone levels.

Parameters:
    city — City name to check air quality for (required), e.g. "London".

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

Input Schema

Name	Required	Description	Default
`city`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.1Jun 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description bears full responsibility. It transparently explains the underlying API (Open-Meteo, free, no key) and the geocoding step, and lists the returned pollutants. It does not mention rate limits or error handling, but the key behavioral traits are covered.

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 extremely concise: two sentences plus a param line. Every word adds value, and the most important information is front-loaded.

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?

Given the single parameter and existence of an output schema, the description adequately covers what the tool does and returns. It mentions the API source and data points. Minor missing details about geocoding failures or return format could be included, but overall it is sufficient for a simple tool.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates well by explaining the 'city' parameter as a required city name with an example ('London'). This adds meaning beyond the schema's bare 'string' type.

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 clearly states the tool gets current air quality data for any city, specifying the output (European AQI, US AQI, PM2.5, etc.). It is specific and distinct from sibling tools like get_weather or get_forecast.

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 does not explicitly guide when to use this tool over alternatives. It implies use for air quality queries but offers no exclusions or comparisons to similar tools, leaving the agent to infer context.

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

Deploy Server