Belgium Data Desk

Air quality at a place in Belgium (now, forecast, annual)

air_quality

Read-only

Air quality at an address or point anywhere in Belgium from IRCEL-CELINE, read live: this hour's modelled NO2, PM2.5, PM10, ozone and black carbon for the 4 km cell, the last 24-hour PM means against the WHO 24-hour guidelines, the BelAQI forecast for today and the next three days (1 excellent to 10 horrible), annual means of the last complete year (street level in Flanders via ATMO-Street, 4 km background elsewhere) compared with the WHO 2021 guidelines and the current and 2030 EU limit values, and the nearest measuring stations that are reporting now (out-of-service stations are skipped and named). Includes the municipality (NIS code) with its population and income. Starts with key_facts; cite IRCEL-CELINE (CC BY 4.0). Examples: How is the air in central Brussels now, and over the year? → {"address":"Rue Neuve 1, 1000 Bruxelles"}; Air quality forecast for Liège → {"address":"Place Saint-Lambert 1, 4000 Liège"}; Annual NO2 at street level near Antwerp central station → {"latitude":51.2194,"longitude":4.4025}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "air_quality"
  }
}

Input Schema

Name	Required	Description
`address`	No	Address in Belgium, e.g. 'Grote Markt 1, 3000 Leuven' or 'Place Saint-Lambert 1, 4000 Liège'.
`latitude`	No	WGS84 latitude, e.g. 51.0453 (use with longitude instead of address).
`longitude`	No	WGS84 longitude, e.g. 3.7275.
`x_lambert72`	No	Belgian Lambert 72 (EPSG:31370) x in metres, as an alternative to latitude/longitude.
`y_lambert72`	No	Belgian Lambert 72 (EPSG:31370) y in metres.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description still adds real value beyond that: the upstream source, CC BY 4.0 attribution obligation, 'starts with key_facts' response ordering, that out-of-service stations are skipped and named, and the modelled-vs-street-level distinction.

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?

The payload enumeration is front-loaded and every clause conveys distinct content (pollutants, guidelines, forecast scale, annual source, stations). It is a single very dense sentence, though, and the parenthetical BelAQI scale and licensing note slightly lengthen an already heavy block.

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?

With no output schema, the description correctly carries the burden of describing what comes back, including the key_facts lead field and the comparison baselines (WHO 2021, EU current/2030). It stops short of describing the shape of key_facts or what happens for out-of-Belgium coordinates, so it is strong but not exhaustive.

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 each of the five parameters is documented with an example, so the schema does the heavy lifting; baseline 3 applies. The description's phrase 'address or point' and the examples (address form for Brussels/Liège, lat/lon for Antwerp) add only modest routing guidance between the input modes, and it never mentions the Lambert 72 alternative.

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?

Names a specific verb+resource (air quality at a place) and enumerates the exact payloads: current hour modelled pollutants, 24-hour PM means vs WHO, BelAQI forecast for today plus three days, annual means, and nearest reporting stations. The scope ('anywhere in Belgium', source IRCEL-CELINE) is unambiguous and clearly distinct from weather or river_levels siblings.

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?

Three worked examples map natural queries ('How is the air in central Brussels now, and over the year?') to concrete inputs, which implicitly tells the agent when this tool applies. What is missing is an explicit exclusion or sibling routing (e.g., when to prefer weather, or that street-level detail only applies in Flanders).

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

All Belgium Data Desk tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.