Luxembourg MCP

get_air_quality

Retrieve national telemetric air-quality measurements from monitoring stations across Luxembourg. Filter results by city to get specific station data.

Instructions

Get the latest national telemetric air-quality measurements by station.

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": "get_air_quality"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No	Optional city-name filter

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 11, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions 'latest' but does not specify update frequency, data freshness, authentication needs, or rate limits. The term 'telemetric' hints at real-time data but lacks clarity.

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?

A single sentence conveys the core purpose with no redundancy. Every word is necessary and the structure is front-loaded with the action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of air quality data (multiple pollutants, units, stations), the description lacks details about return format, data fields, or pagination. No output schema exists, so the description should compensate.

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 description coverage is 100%, so the parameter 'city' is already documented with 'Optional city-name filter'. The tool description adds no additional semantics about format, examples, or behavior when omitted. Baseline score of 3 is appropriate.

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 action ('Get'), the resource ('latest national telemetric air-quality measurements'), and the context ('by station'). This distinguishes it from sibling tools like 'get_traffic' or 'get_weather_observations'.

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?

No guidance is provided on when to use this tool vs. alternatives such as 'get_weather_observations' or 'get_water_levels'. The description does not mention prerequisites, limitations, or exclusions.

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