Saharan dust vs. anthropogenic emissions — CAMS/Copernicus air-quality analysis with UBA ground-truth station overlay
Server has 5 tools with complete input schemas and descriptions. Naming follows verb_noun pattern (analyze_, show_, compare_, query_, data_). Descriptions are present but vary in quality, some are terse (German labels without English context). Parameters have types and descriptions, but lack enums for constrained values (e.g., 'mode' and 'variable' accept free-form strings instead of declared enums). Output schemas are not documented in tool definitions. Error handling exists but is minimal. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being READ_ONLY. Composition is sound, each tool has one responsibility. Security is adequate (no secrets in params, all tools are read-only).
Zeitreihe fur Saharastaub, SO2 und PM2.5 an einem europaischen Standort. Empfohlener Einstieg fur jede Luftqualitats-Frage.
Mehrere Stadte vergleichen - max 5
Report what data is available in the remote release
Bereits heruntergeladene Daten abfragen - kein API-Call
Raumliche Verteilung auf Karte - Heatmap auf OpenStreetMap
Descriptions are in German without English translation, limiting LLM understanding. E.g., 'Zeitreihe fur Saharastaub...' and 'Raumliche Verteilung auf Karte' are opaque to English-language models.
Parameters 'mode' (analyze_air_quality), 'variable' (show_air_quality_map, compare_cities), and 'data_type' (query_measurements) accept free-form strings but should declare enums. LLMs will hallucinate invalid values.
No tool annotations despite all tools being READ_ONLY. Missing readOnlyHint in tool metadata prevents LLM from understanding safety properties.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2025-06-18+ | v2 |
Output schemas are not documented. Tool descriptions do not specify what fields are returned or their types. LLMs cannot plan downstream calls or extract data reliably.
data_availability tool has empty input schema (no parameters) but description is vague ('Report what data is available'). Unclear what triggers the report or what format is returned.