Skip to main content
Glama
street1983nk

InfraNode

by street1983nk
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Deutsch | English

InfraNode

GitHub stars License: Apache 2.0 Glama score MCP Registry Smithery

Die Open-Data-REST-API für Deutschland: eine HTTP-API ohne API-Key für Open Data zur öffentlichen Infrastruktur, auch als MCP-Server verfügbar.

Deutsche Städte veröffentlichen viel Open Data, aber jede Quelle hat ihr eigenes Format, eigene Felder und eigene Eigenheiten, und für mehrere braucht es eine Registrierung im jeweiligen Portal. InfraNode normalisiert rund 20 Kategorien, Wetter (DWD), Luftqualität (UBA), ÖPNV (inklusive Echtzeit-Abfahrten), Verkehr, Strompreis (SMARD), Bodenrichtwerte (BORIS), Parken, Ladeinfrastruktur, Pegelstände, Demografie, Energie und mehr, für 84+ deutsche Städte hinter einer Schnittstelle. Kein API-Key, kein Konto. Jede Antwort nutzt denselben kanonischen { data, meta }-Umschlag mit Lizenz und Attribution je Datensatz. Dieselben Daten stehen KI-Agenten auch als MCP-Server zur Verfügung (12 schlanke Read-only-Tools über 78 Datenarten). Der Einstieg ist get_city_overview, ein einziger Aufruf: Er liefert einen Katalog aller Datenarten, die es für eine Stadt gibt, dazu einen Live-Auszug der wichtigsten Werte. So sehen Agenten die volle Breite und nicht nur das Wetter. InfraNode wächst laufend, neue Datenarten und Städte kommen regelmäßig dazu.

Zu den Quellen gehören der Deutsche Wetterdienst (DWD), das Umweltbundesamt (UBA), Mobilithek/DELFI, der VBB (Verkehrsverbund Berlin-Brandenburg, CC-BY 4.0), GovData, OpenStreetMap, die Bundesnetzagentur, das KBA und weitere.

Im Einsatz

InfraNode-Live-Übersicht für Köln: aktuelles Wetter, amtliche Luftqualität, DWD-Warnungen, Live-Zugabfahrten mit Verspätungen, Baustellen und der vollständige Katalog der Datenarten, alles aus einem Aufruf ohne API-Key

Ein einziger get_city_overview("koeln")-Aufruf: aktuelles Wetter, amtliche Luftqualität, DWD-Warnungen, Live-Zugabfahrten mit Verspätungen, Baustellen und der vollständige Datenkatalog der Stadt, aus einem Endpoint ohne API-Key. Jede Stadt lässt sich live ausprobieren auf infranode.dev.

Related MCP server: germany-mcp-server

So funktioniert es

Ein gemeinsamer HTTP-Client fragt die Upstream-Quellen ab, jede Antwort wird auf das kanonische Schema abgebildet, mit ihrer Attribution durch das Lizenz-Gate geführt und in Redis zwischengespeichert (mit Stale-on-Error-Fallback), danach über eine REST-API und einen MCP-Server ausgeliefert. Fällt eine Quelle aus, schlägt sich das in source_status nieder. Der Aufruf selbst scheitert nie daran.

flowchart LR
    subgraph SRC["25+ deutsche Open-Data-Quellen"]
        direction TB
        S1["DWD, UBA<br/>Wetter, Luft"]
        S2["Mobilithek, DELFI, DB<br/>ÖPNV, Echtzeit"]
        S3["SMARD, BNetzA, MaStR<br/>Energie"]
        S4["BORIS, GovData, OSM,<br/>KBA, ..."]
    end

    subgraph CORE["InfraNode-Kern"]
        direction TB
        N["Normalisieren<br/>ein kanonisches Schema"] --> L["Lizenz-Gate<br/>Attribution je Datensatz"] --> C["Redis-Cache<br/>Stale-on-Error-Fallback"]
    end

    SRC --> CORE
    CORE --> API["REST-API<br/>infranode.dev/api/v1<br/>84 Städte, ohne API-Key"]
    CORE --> MCP["MCP-Server<br/>mcp.infranode.dev<br/>12 Read-only-Tools"]
    API --> APPS["Apps &amp; Dashboards"]
    MCP --> AGENTS["KI-Agenten<br/>Claude, ChatGPT"]

Wenn InfraNode dir eine Datenintegration erspart: Ein Stern hilft anderen Entwicklern, das Projekt zu finden.

Schnellstart

Basis-URL https://infranode.dev/api/v1. Kein Key, kein Konto, einfach aufrufen:

curl https://infranode.dev/api/v1/cities/koeln/weather
{
  "data": {
    "city_slug": "koeln",
    "observed_at": "2026-06-18T13:00:00Z",
    "source": "dwd",
    "attribution": { "text": "Datenbasis: Deutscher Wetterdienst", "modified": true },
    "payload": { "kind": "weather", "temperature_c": 30.4, "humidity": 43.0, "station_id": "02667" }
  },
  "meta": { "source_status": "ok", "cache_status": "hit", "correlation_id": "..." }
}

Jede Antwort folgt demselben { data, meta }-Umschlag: Jeder Datensatz trägt seine attribution (Lizenz und Quelle), und meta.source_status sagt, ob die Upstream-Quelle Daten geliefert hat. Eine tote Quelle degradiert damit sauber, statt den Aufruf scheitern zu lassen.

Über alle Datenarten hinweg sind Feldnamen snake_case und englisch, und dasselbe Konzept heißt immer gleich: post_code, street, house_number, place, name, start, end, distance_km, power_kw, lat, lon. post_code ist immer ein fünfstelliger String (führende Nullen bleiben erhalten), Zeitstempel sind ISO 8601 mit Zeitzone, und ein Wert, den die Quelle nicht liefert, ist null, nie ein leerer String. Manche Antworten führen daneben noch ältere Doppelnamen mit identischen Werten (plz, zip, strasse, hausnummer, ort, city, bezeichnung, beginn, ende, art, dist_km, leistung_kw, einheit_typ, dazu die camelCase-Rohfelder der Autobahn-Verkehrsmeldungen). Diese Namen sind veraltet, nimm die kanonischen.

Tipp: Ruf zuerst /api/v1/cities auf, um die kanonischen Stadt-Slugs zu finden (etwa koeln, berlin, hamburg), und danach einen stadtbezogenen Endpoint.

Der {slug} wird tolerant aufgelöst, die exakte ASCII-Form brauchst du also selten: der deutsche Name mit oder ohne Umlaute, jede Groß- und Kleinschreibung, gängige englische Exonyme und Kurzformen führen alle auf den kanonischen Slug (München/münchen/munich/munchen → muenchen, cologne → koeln, frankfurt → frankfurt-am-main). Ein unbekannter Name liefert 404 mit dem Hinweis Meintest du ...?, der den nächstliegenden Slug nennt.

Run in Postman

Die vollständige interaktive Referenz und die Abdeckung je Stadt stehen auf infranode.dev. Die InfraNode API im Postman API Network spiegelt jeden Endpoint mit echten Beispielantworten, sodass sich die InfraNode API Postman Collection ohne API-Key direkt im Browser ausprobieren lässt.

Daten (84 Städte, 124 Endpunkte)

Jede Kategorie unten ist ein REST-Endpoint unter /api/v1/cities/{slug}/<key>. Über MCP kommen dieselben Daten durch 12 schlanke Tools: ein paar benannte (get_city_overview, weather, air_quality, pois, compare, die Live-Tafeln) und ein generisches get_city_resource(slug, resource=<key>) für jede weitere Datenart (sein resource-Enum listet alle 81 Keys).

Gruppe

Datenarten (Endpoint-Keys)

Entdecken

list_cities, sources, compare (eine Datenart über viele Städte), overview (Katalog plus Live-Auszug in einem Aufruf)

Wetter & Umwelt

weather, weather-warnings, civil-protection-warnings (BBK NINA), air-uba (amtlich), air (live), pollen-uv, water-level, flood, fire-danger, bathing-water

Mobilität

transit, Live-Abfahrten je Haltestelle (Tool transit_departures), stations (Katalog), Bahnhofstafeln nach EVA (Tools station_board_departures/station_board_arrivals, inklusive Nahverkehr und Störungen), station-departures, station-arrivals, traffic, road-events, webcams, charging, parking (Live-Belegung), parking-onstreet, park-and-ride, mobility-points, bike-parking, sharing, fuel-prices, bike-counts

Stadt & Menschen

base, geo, demographics, indicators, sustainability (SDG-Indikatoren je Kommune als Zeitreihe 2006-2023, Wegweiser Kommune / Bertelsmann Stiftung, CC0), unemployment, tourism, construction, accidents, crime-stats, health, icu-live, holidays, election, events, council-papers (kommunale Ratsinformationen über OParl: Vorlagen, Anträge und Beschlüsse je Stadt), pois, Spielplätze, Märkte, Toiletten und weitere OSM-Typen

Wirtschaft & Immobilien

land-values, tax-rates (Hebesätze für Gewerbe- und Grundsteuer je Kommune), business-registrations (Gründungsdynamik je Kreis), insolvencies (Insolvenzverfahren je Kreis: Unternehmen und übrige Schuldner, jährlich), public-tenders (öffentliche Vergabe: laufende Ausschreibungen und vergebene Aufträge je Stadt)

Energie & Fahrzeuge

power-load, power-price, energy, solar, solar-roofs, district-heating, vehicle-registrations

Verhalten im Betrieb

  • Ohne Key, nur lesend. Keine Zugangsdaten, keine Schreibzugriffe, keine Nutzerkonten.

  • Kanonischer Umschlag. { data, meta } mit Status und Attribution je Quelle.

  • Sanfte Degradation. Eine ausgefallene Quelle liefert source_status, keinen Fehler.

  • Sicher entworfen. SSRF- und Injection-Gates prüfen jede Anfrage, Eingaben laufen gegen feste Allowlists.

Das Sicherheitsmodell steht in SECURITY.md.

Paginierung & Kanal-Voreinstellungen

Listen von Datenarten (charging, energy, events, transit, die OSM-Feature-Endpoints) haben bei gleicher URL eine kanalabhängige Voreinstellung:

  • Direktes REST liefert die vollständige Liste in einem Aufruf (limit=null, returned == total, truncated=false).

  • GPT Actions (OpenAI-Header) und MCP sind an eine voreingestellte Seitengröße gebunden, damit Antworten für Agenten klein bleiben.

  • limit=all (oder ?all=1) erzwingt auf jedem Kanal die volle Liste, limit und offset blättern explizit.

  • meta.pagination (total/returned/limit/offset/truncated) steht auf jedem Kanal, der ausgelieferte Ausschnitt ist also immer nachvollziehbar.

Bei traffic ist die rohe Polyline optional: include=geometry (oder ?full=1) ergänzen, die Standardantwort bleibt schlank.

Stabilität, Changelog & Roadmap

Du baust produktiv auf InfraNode auf? Dann bleib bei Änderungen vorne:

  • Changelog listet jede sichtbare Änderung (neue Datenarten, neue Städte, geändertes Verhalten, Fehlerbehebungen, Deprecations), die neueste zuerst. Per RSS abonnierbar.

  • Roadmap zeigt das Geplante und die Stabilitätszusage: Die API wächst additiv, der Umschlag bleibt stabil, und Änderungen an bestehenden Antworten werden vorher angekündigt (in der Regel 30+ Tage).

  • Statusseite und die GitHub-Releases decken Verfügbarkeit und versionierte Änderungen ab.

Als MCP-Server nutzen

Dieselbe API steht als Remote-MCP-Server bereit, KI-Agenten können also alle 78 Datenarten als Tools aufrufen. Mit Claude Code genügt eine Zeile:

claude mcp add --transport http infranode https://mcp.infranode.dev/mcp

Jeden anderen MCP-Client richtest du auf denselben Remote-Endpoint (Streamable HTTP):

{
  "mcpServers": {
    "infranode": { "url": "https://mcp.infranode.dev/mcp" }
  }
}

  • Cursor / Windsurf: den Block oben in ~/.cursor/mcp.json eintragen (oder in die MCP-Einstellungen der App).

  • VS Code: code --add-mcp '{"name":"infranode","url":"https://mcp.infranode.dev/mcp"}'

  • Claude Desktop: denselben mcpServers-Block in die claude_desktop_config.json eintragen.

  • ChatGPT: einen Connector mit der URL https://mcp.infranode.dev/mcp anlegen.

Alle Tools tragen die Annotationen readOnlyHint: true / destructiveHint: false / idempotentHint: true, MCP-Clients können sie also gefahrlos automatisch freigeben. Die MCP-Schicht bringt außerdem fertige Prompts (city_briefing, compare_air_quality, commute_check) und Ressourcen (infranode://cities, infranode://sources) mit. Die vollständige Installationsanleitung, das komplette Tool-Manifest mit Beispielausgaben, das Berechtigungsmodell und ein Beispiel-Transkript stehen in docs/mcp-install.md. Das Registry-Manifest ist server.json.

In ChatGPT nutzen (Custom-GPT-Action)

Fertiges GPT: InfraNode: German City Data - Weather & Transit steht im GPT Store (Research & Analysis) und funktioniert sofort.

Für eine eigene Variante liefert InfraNode eine kuratierte OpenAPI-Spec für GPT-Actions: 23 der nützlichsten Operationen (ChatGPT erlaubt höchstens 30 pro Action), ohne Key, alle GET.

  1. Im GPT-Editor Configure → Actions → Create new action → Import from URL öffnen und https://infranode.dev/actions/openapi.json einfügen.

  2. Die Authentifizierung auf None stehen lassen, als Datenschutzerklärung https://infranode.dev/datenschutz/ eintragen.

  3. In den Instructions des GPT festhalten: mit getCityOverview(slug) starten, Stadtnamen über getCities auflösen und data.attribution zitieren (die Datenlizenzen verlangen die Namensnennung).

Details und empfohlene Instructions: infranode.dev/chatgpt/. Die Spec wird von scripts/build_actions_spec.py aus docs/openapi.yaml erzeugt.

Alternativen und wie InfraNode dazu steht

Andere MCP-Server decken Teile des deutschen oder europäischen Datenraums ab. Für Open Data auf Stadtebene ist InfraNode am breitesten, und die Projekte unten ergänzen einander oft:

  • germany-mcp-server Bundes- und Regierungsdaten (Autobahn, DWD, NINA, SMARD, Bundestag). Bundesweit, ohne Tiefe je Stadt.

  • db-mcp-server / db-timetable-mcp nur Fahrpläne der Deutschen Bahn.

  • mcp-server-public-transport ÖPNV in Europa, in Deutschland deckt es Berlin/Brandenburg (VBB) ab.

  • Server für einzelne Städte (etwa München, Berlin) decken je eine Stadt ab.

InfraNode deckt 84 deutsche Städte und 82 Datenarten hinter einem gehosteten Endpoint ohne API-Key ab: Umwelt, Mobilität, Energie, Wirtschaft und Stadtleben. Der vollständige Vergleich Seite an Seite steht auf infranode.dev/mcp-vergleich.

Selbst hosten (optional)

Nötig ist das nicht, der gehostete Endpoint oben ist der schnellste Weg. Der Code liegt aber offen. Den API-Stack lokal mit Docker (Compose v2) starten:

cp .env.example .env          # example config, contains NO real secrets
docker compose -f deploy/docker-compose.yml up
curl http://localhost/api/v1/health   # -> {"status":"ok","version":"1.0.0","redis":true}

Den MCP-Server selbst lokal über stdio betreiben (gegen die öffentliche API):

uv sync --group mcp
INFRANODE_MCP_API_BASE=https://infranode.dev/api/v1 uv run python -m infranode.mcp.server

Für alle Einstellungen gilt das Env-Präfix INFRANODE_ (siehe .env.example), jede Datenquelle hat ihren eigenen INFRANODE_ENABLE_*-Schalter. Echte Secrets landen nie im Repo, versioniert ist nur .env.example, und die CI fährt einen gitleaks-Scan.

Lizenz: Code und Daten sind getrennt

  • Code: Apache-2.0 (siehe LICENSE).

  • Daten: Die offenen Daten, die InfraNode ausliefert, behalten die Lizenzen ihrer Upstream-Quellen (etwa ODbL für OpenStreetMap, DL-DE-BY für GovData, Namensnennung für DWD). Diese Datenlizenzen und die Attribution werden separat in DATA-LICENSES.md geführt. Die Apache-2.0-Lizenz gilt nur für den Quellcode der API, nicht für die durchgereichten Daten.

Mitmachen

Beiträge sind willkommen. Setup, Gate-Befehle und die Secret-Regel stehen in CONTRIBUTING.md. Für eine neue Datenquelle ist die deklarative Quellen-Registry in src/infranode/registry/source_specs.py der Startpunkt (ein SourceSpec-Eintrag je Upstream), die vollständige Checkliste steht in CONTRIBUTING.md.

Available Tools

12 tools
air_qualityAir QualityA
Read-onlyIdempotent
Inspect

Get official air quality for a German city (PM10, NO2 and more).

Sourced from the Umweltbundesamt (UBA). Read-only. For live nearest-station hourly readings use get_city_resource(slug, resource='air') instead.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesCity slug from the list_cities tool, e.g. 'berlin' or 'hamburg'.

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.5/5.0
Behavior4/5

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

While annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, the description adds value by stating the data source (Umweltbundesamt) and the specific pollutants included (PM10, NO2), enriching behavioral context without contradiction.

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 two sentences long, front-loaded with the main purpose, followed by source and alternative usage. Every sentence serves a clear function with no waste.

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 single parameter, existing output schema, and annotations covering safety, the description fully covers the tool's functionality, including what data is returned and its official nature.

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% with a clear description of the 'slug' parameter referencing list_cities. The description does not add new parameter details beyond the schema, so a baseline 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 explicitly states 'Get official air quality for a German city (PM10, NO2 and more),' specifying the verb, resource, and scope. It differentiates from sibling tools by mentioning an alternative for live readings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-not-to-use guidance: 'For live nearest-station hourly readings use get_city_resource(slug, resource='air') instead,' and names the alternative tool.

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

compareCompare CitiesA
Read-onlyIdempotent
Inspect

Compare ONE resource across MULTIPLE cities in a single response.

Fans the resource out over the listed cities and returns a per-city source_status (ok/disabled/no_data/error/not_found), so a missing or failing city source does not spoil the whole answer. Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault
citiesYesComma-separated list of city slugs, e.g. 'berlin,koeln,hamburg' (max. 28 cities).
resourceYesResource to compare. Supported: 'weather' (DWD), 'air' (UBA air quality), 'indicators' (INKAR socioeconomic indicators incl. unemployment rate and EV charging coverage), 'demographics', 'unemployment', 'tourism', 'charging-status' (live EV charging occupancy, aggregates only) and 'weather-warnings' (official DWD warning level per city).

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable behavioral context: the tool fans out the resource across cities and returns a per-city source_status, ensuring that a failing city does not spoil the whole response. This goes beyond the annotations.

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 three sentences long, front-loaded with the core action, no fluff. Every sentence provides value: purpose, behavior, and read-only nature.

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 (2 params, fully described in schema, output schema present), the description is complete. It explains the key behavioral aspect (per-city source_status) and does not miss critical information.

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 both parameters are well-described. The description reinforces the purpose but does not add new meaning beyond what the schema provides. Baseline 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 tool compares ONE resource across MULTIPLE cities in a single response. The verb 'compare' and the explicit 'ONE resource' and 'MULTIPLE cities' differentiate it from sibling tools like get_city or get_city_resource, which operate on a single city.

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 description implies when to use this tool: when you need to compare a resource across multiple cities in one call. It does not explicitly state when not to use it or mention alternatives, but the context is clear enough for an agent to infer appropriate usage.

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

get_cityCity Base DataA
Read-onlyIdempotent
Inspect

Get base data for a German city (population, area, coordinates).

Sourced from Wikidata. Read-only. Useful as a first lookup to confirm a city exists and get its core attributes. For a broader question about the city (what data is available at all) use get_city_overview instead.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesCity slug from the list_cities tool, e.g. 'berlin' or 'hamburg'.

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. Description adds 'Sourced from Wikidata. Read-only.' but this adds only minor context beyond the annotations.

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?

Three sentences, each valuable: purpose, source, usage guidance with alternative. No wasted words. Front-loaded with primary action.

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?

Tool has output schema (not shown but present), so return values are covered. Description covers purpose, source, and usage context. For a simple read-only lookup with one parameter, this is complete.

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 provides full description for the single required parameter 'slug' (coverage 100%). The tool description does not add any extra meaning beyond the schema's description.

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 'Get base data for a German city' with specific attributes listed. It distinguishes from sibling tool `get_city_overview` by focusing on base data only.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Useful as a first lookup to confirm a city exists and get its core attributes.' Provides an alternative: 'For a broader question... use get_city_overview instead.'

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

get_city_overviewCity OverviewA
Read-onlyIdempotent
Inspect

Get a ONE-CALL overview of everything InfraNode knows about a German city.

Start here for any city question. Returns: the city's base data, a CATALOG of all 67 available data types (weather, air quality, public transit, trains, traffic, charging, parking, solar, energy, demographics, taxes, accidents, tourism, heritage, trees, population density, playgrounds, post boxes and many more), each with its coverage status and the exact tool to call next (for most data types that is get_city_resource(slug, resource=<type>)), plus a small live highlights snapshot (current weather, air quality and train departures). Data types not yet covered for this city show where they ARE available so you can pivot. InfraNode keeps adding data and cities, so the catalog grows over time. Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesCity slug from the list_cities tool, e.g. 'berlin' or 'hamburg'.

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint. The description adds valuable behavioral context: it returns a catalog of 67 data types with coverage status, a live highlights snapshot, and redirection for uncovered data. It also declares the tool as read-only, consistent with annotations.

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 concise (~6 sentences) and front-loaded with the main purpose. Every sentence adds essential information without redundancy, and the structure follows a logical flow: purpose, return components, future growth.

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 there is an output schema (implied by context signals), the description appropriately focuses on the high-level structure (base data, catalog, highlights). It covers the dynamic nature of the catalog and provides enough context for the agent to understand the tool's role without needing full return details.

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?

With 100% schema description coverage for the single parameter 'slug', the baseline applies. The schema already provides clear documentation. The description does not add additional parameter semantics, which is acceptable given the coverage.

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 uses specific verbs ('Get a ONE-CALL overview') and clearly defines the resource ('everything InfraNode knows about a German city'). It distinguishes from sibling tools by positioning itself as the starting point and listing the returned catalog with pointers to other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states 'Start here for any city question' and explains that for specific data types, users should call tools like get_city_resource. This provides clear when-to-use and alternatives guidance.

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

get_city_resourceCity Data by TypeA
Read-onlyIdempotent
Inspect

Fetch ANY per-city data type by its key (generic accessor, 67 data types).

One tool for the whole breadth of InfraNode: live data (air, traffic, transit stops, parking, charging, water-level, flood, sharing, fuel-prices, icu-live, webcams, station-departures/-arrivals/stations, ...), statistics (demographics, unemployment, tourism, accidents, crime-stats, indicators, land-values, tax-rates, insolvencies, ...), infrastructure and environment (solar, solar-roofs, district-heating, energy, heritage, tree-cadastre, playgrounds, public-toilets, markets, education, ...) and more. Discover the valid keys and per-city coverage with get_city_overview(slug) or the infranode://catalog resource; the resource enum lists every key. Uncovered types return source_status="not_covered" (plus where they ARE available), never an error. Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesCity slug from the list_cities tool, e.g. 'berlin' or 'hamburg'.
resourceYesData type key to fetch, exactly as listed by get_city_overview / the infranode://catalog resource (the 'type' field), e.g. 'charging', 'parking', 'demographics', 'solar', 'district-heating'.

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotent. Description adds 'Read-only' and explains error-free handling for uncovered types ('source_status="not_covered"'), providing useful behavioral context beyond annotations.

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?

Front-loads purpose, uses a bullet-like enumeration of example types for clarity, and is efficient. Slightly verbose with the long type list, but overall concise and well-structured.

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 tool's generic nature (67 types) and presence of an output schema, the description adequately covers key discovery, coverage behavior, and safety. Complete enough for effective use.

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%; the description adds value by listing examples and explaining how to discover keys, but does not fundamentally extend meaning beyond the schema parameters.

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?

Description clearly states 'Fetch ANY per-city data type by its key', specifying verb, resource, and scope. It distinguishes from siblings by noting it is a generic accessor for 67 data types, unlike more specialized tools like air_quality or weather.

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?

Explicitly tells users to discover valid keys via get_city_overview or catalog, and explains that uncovered types return a specific status instead of error. However, it does not explicitly state when NOT to use this tool in favor of siblings.

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

list_citiesList CitiesA
Read-onlyIdempotent
Inspect

List all covered cities (slug, federal state, population, coverage).

Takes no arguments. Call this first to discover valid city slugs before invoking any city-scoped tool. Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description reaffirms read-only and adds output field context, which is valuable beyond annotations.

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?

Two sentences, zero wasted words. Front-loaded with the core action and output, then usage instruction.

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 zero parameters, rich annotations, and output schema, the description is fully complete. It covers purpose, output, and usage order.

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?

No parameters, so baseline 4. The description adds value by listing the output fields, aiding in understanding the tool's response.

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 specifies the verb 'List', the resource 'all covered cities', and the output fields (slug, federal state, population, coverage). It distinguishes from siblings by establishing the tool as a prerequisite for city-scoped tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'Call this first to discover valid city slugs before invoking any city-scoped tool.', providing clear when-to-use guidance and establishing a dependency.

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

poisPoints of InterestA
Read-onlyIdempotent
Inspect

Get points of interest in a German city, filtered by type.

Sourced from OpenStreetMap. Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesCity slug from the list_cities tool, e.g. 'berlin' or 'hamburg'.
typeYesPOI type from the API allowlist, one of: hospital, school, pharmacy, restaurant, police, kindergarten.

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds context about data sourcing from OpenStreetMap, which is not covered by annotations. No contradictions found.

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?

Two sentences: first states the core purpose, second adds essential context (source and read-only). No filler, front-loaded, every sentence adds value.

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 presence of an output schema, the description does not need to explain return values. It covers purpose, geographic scope (German city), filter (type), and data source. Lack of pagination or result limit details is acceptable for read-only tools with annotations.

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 parameters are well-documented in the schema. The description merely repeats 'filtered by type' without adding new meaning beyond what the schema already provides.

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's action ('Get'), resource ('points of interest'), and key filters ('in a German city', 'filtered by type'). It also mentions the data source (OpenStreetMap) and read-only nature, distinguishing it from sibling tools like list_cities or get_city.

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 explicit guidance on when to use this tool versus alternatives. While the purpose is clear, the description lacks information about prerequisites, exclusions, or comparisons with siblings like get_city_overview or sources.

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

sourcesData SourcesA
Read-onlyIdempotent
Inspect

List all data sources with license, attribution and availability.

Takes no arguments. Shows which upstream sources InfraNode bundles and whether each is currently active. Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds that it shows whether each source is currently active, which is not in annotations. No contradiction.

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?

Three sentences, concise and front-loaded with the core purpose. No wasted words, and every sentence adds value.

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 no parameters, clear annotations, and existing output schema, the description fully covers what the tool does and returns. It is complete for an agent to understand its purpose and behavior.

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?

There are no parameters, so the description does not need to add param info. Schema coverage is 100%, and the baseline for no params is 4. The description 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 it lists data sources with license, attribution, and availability, and shows activity status. The verb 'List' and resource 'data sources' are specific, and it distinguishes from sibling tools like 'air_quality' or 'transit_departures' which focus on specific data types.

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 description explains that the tool takes no arguments and is used to see which upstream sources are bundled. While it doesn't explicitly state when not to use or name alternatives, the context of being a listing tool for available data sources is clear.

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

station_board_arrivalsStation Board: ArrivalsA
Read-onlyIdempotent
Inspect

Get live arrivals for ANY railway station by its EVA number.

Mirror of station_board_departures for arriving trains (all categories, real-time delays, disruption messages). Get the EVA from get_city_resource(slug, resource='stations'). Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault
evaYesStation EVA number (digits only) from get_city_resource(slug, resource='stations'), e.g. '8000105' (Frankfurt Hbf).

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds behavioral details: 'live arrivals', 'all categories, real-time delays, disruption messages', which goes beyond annotations. No contradiction.

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 three sentences with no extraneous words. The main purpose is front-loaded, and every sentence adds value.

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, output schema present, annotations covering safety), the description provides all necessary context: purpose, input source, read-only nature, and differentiation from departures.

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?

Schema coverage is 100%. The description adds meaning by specifying the EVA number must be 'digits only' and provides an example, as well as referencing the helper function to obtain it.

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 'Get live arrivals for ANY railway station by its EVA number', specifying the verb, resource, and scope. It distinguishes itself from the sibling 'station_board_departures' by noting it is a mirror for arrivals.

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 description tells when to use the tool (to get arrivals) and provides guidance on obtaining the EVA number via 'get_city_resource'. It implicitly contrasts with departures, but lacks explicit 'when not to use' statements.

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

station_board_departuresStation Board: DeparturesA
Read-onlyIdempotent
Inspect

Get live departures for ANY railway station by its EVA number.

Covers all train categories including local/regional (S/RB/RE) and long distance, with real-time delays, cancellations and disruption messages. Get the EVA from get_city_resource(slug, resource='stations'). Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault
evaYesStation EVA number (digits only) from get_city_resource(slug, resource='stations'), e.g. '8011160' (Berlin Hbf).

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, etc. The description adds value by detailing the nature of data (real-time delays, cancellations, disruptions) and reaffirming 'Read-only'. This goes beyond annotations but could still mention rate limits or data freshness.

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 with three sentences, each serving a distinct purpose: action + scope, coverage details, prerequisite. No wasted words, and the most important information (live departures) 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 (1 parameter, output schema exists), the description covers all essential aspects: what it returns, the required input, and how to obtain it. No significant gaps remain.

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?

Schema description coverage is 100% and already explains the 'eva' parameter well. The description adds useful context by referencing get_city_resource as the source for the EVA number, which aids in parameter preparation. This exceeds the baseline of 3.

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 specifies the action ('Get live departures'), resource ('ANY railway station by its EVA number'), and scope ('all train categories ... with real-time delays, cancellations and disruption messages'). It distinguishes from siblings by focusing on departures and specifying coverage, though not explicitly differentiating from station_board_arrivals.

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 description provides clear context for when to use the tool (live departures for any station) and a prerequisite (get EVA from get_city_resource). However, it lacks explicit guidance on when not to use it (e.g., for arrivals) or reference to alternatives like station_board_arrivals.

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

transit_departuresTransit DeparturesA
Read-onlyIdempotent
Inspect

Get live public-transport departures with real-time delays for a stop.

Sourced from GTFS-RT/HVV/VGN. Unlike the static stop list (get_city_resource(slug, resource='transit')), this returns minute-fresh departures including delay for ONE stop. A stop_id is required: fetch the city's transit stops first to discover valid stop IDs, then pass one here. Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesCity slug from the list_cities tool, e.g. 'berlin' or 'hamburg'.
stop_idNoRequired stop ID to fetch departures for. Discover a city's stop IDs with get_city_resource(slug, resource='transit') first (each stop carries its id). Format: DELFI 'de:<AGS>:<id>' or a numeric gtfs.de stop id.

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent), the description adds context: 'minute-fresh departures including delay for ONE stop', data source ('GTFS-RT/HVV/VGN'), and the requirement for a stop ID. It does not contradict any annotations.

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 concise yet informative, with four sentences each serving a distinct purpose: stating the main function, citing the data source, differentiating from a sibling tool, and explaining the prerequisite. No unnecessary words.

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 presence of an output schema (not shown but indicated true) and the complexity of real-time departures, the description provides sufficient context: it clarifies the data source, the real-time nature, the restriction to one stop per call, and the need for prior stop discovery. It fully prepares the agent for correct usage.

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?

Schema coverage is 100%, so both parameters are already described in the input schema. The description adds value by explaining the relationship between `slug` and `stop_id`, noting that `stop_id` must be discovered via another tool, and providing format examples for `stop_id`. This augments the schema without redundancy.

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's purpose: 'Get live public-transport departures with real-time delays for a stop.' It specifies the verb, resource, and scope, and distinguishes itself from the sibling `get_city_resource` by noting it returns dynamic departures for a single stop.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when to use this tool (for live departures with delays) and contrasts it with the static stop list tool, providing an alternative. It also outlines a prerequisite: first fetch transit stops via `get_city_resource(slug, resource='transit')` to obtain valid stop IDs.

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

weatherWeatherA
Read-onlyIdempotent
Inspect

Get current weather observations for a German city.

Sourced from the Deutscher Wetterdienst (DWD): temperature, wind, precipitation and related fields. Read-only, current conditions only (not a forecast). For warnings use get_city_resource(slug, resource='weather-warnings'). For a broader question about the city (not just weather) use get_city_overview instead, which already includes a live weather highlight.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesCity slug from the list_cities tool, e.g. 'berlin' or 'hamburg'.

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
metaYes

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety. The description adds value by specifying data source (DWD), fields (temperature, wind, precipitation), and clarifying it's current conditions only (not forecast). No contradictions with annotations.

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?

Three sentences with no wasted words. First sentence states core purpose, second adds details, third provides usage alternatives. Front-loaded with essential information.

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?

For a simple tool with one parameter and an output schema, the description covers what, source, usage boundaries, and alternatives. Complete for an agent to select and invoke correctly.

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?

Schema coverage is 100% with one parameter 'slug' described. The description adds meaning by stating the slug comes from list_cities tool and giving examples ('berlin' or 'hamburg'), which helps the agent understand valid inputs beyond the schema definition.

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 'Get current weather observations for a German city', specifying verb (Get), resource (weather observations), and scope (German city). It differentiates from siblings by explicitly contrasting with forecasts, weather warnings (get_city_resource), and city overview (get_city_overview).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (current weather), when not (not a forecast), and provides specific alternatives: for warnings use get_city_resource with resource='weather-warnings', and for broader city questions use get_city_overview. This gives clear guidance on tool selection.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.1.1
    • Changedget_city_resource1 field changed
      • changedInput schema / properties / resource / enum
        Previous value: -[
-  "accidents",
-  "air",
-  "air-uba",
-  "base",
-  "bathing-water",
-  "bike-counts",
-  "business-registrations",
-  "charging",
-  "charging-status",
-  "construction",
-  "crime-stats",
-  "demographics",
-  "district-heating",
-  "drinking-water",
-  "education",
-  "election",
-  "energy",
-  "events",
-  "fire-danger",
-  "flood",
-  "fuel-prices",
-  "geo",
-  "government-offices",
-  "health",
-  "heritage",
-  "holidays",
-  "hospitals-atlas",
-  "icu-live",
-  "indicators",
-  "insolvencies",
-  "land-values",
-  "markets",
-  "overview",
-  "parcel-lockers",
-  "parking",
-  "playgrounds",
-  "pollen-uv",
-  "population-density",
-  "post-boxes",
-  "post-offices",
-  "power-load",
-  "power-price",
-  "public-tenders",
-  "public-toilets",
-  "public-wifi",
-  "recycling-centres",
-  "road-events",
-  "sharing",
-  "solar",
-  "solar-roofs",
-  "station-arrivals",
-  "station-departures",
-  "station-facilities",
-  "stations",
-  "tax-rates",
-  "tourism",
-  "traffic",
-  "transit",
-  "tree-cadastre",
-  "unemployment",
-  "vehicle-registrations",
-  "water-level",
-  "weather",
-  "weather-warnings",
-  "webcams"
-]New value: +[
+  "accidents",
+  "air",
+  "air-uba",
+  "base",
+  "bathing-water",
+  "bike-counts",
+  "business-registrations",
+  "charging",
+  "charging-status",
+  "civil-protection-warnings",
+  "construction",
+  "crime-stats",
+  "demographics",
+  "district-heating",
+  "drinking-water",
+  "education",
+  "election",
+  "energy",
+  "events",
+  "fire-danger",
+  "flood",
+  "fuel-prices",
+  "geo",
+  "government-offices",
+  "health",
+  "heritage",
+  "holidays",
+  "hospitals-atlas",
+  "icu-live",
+  "indicators",
+  "insolvencies",
+  "land-values",
+  "markets",
+  "office-wait-times",
+  "overview",
+  "parcel-lockers",
+  "parking",
+  "playgrounds",
+  "pollen-uv",
+  "population-density",
+  "post-boxes",
+  "post-offices",
+  "power-load",
+  "power-price",
+  "public-tenders",
+  "public-toilets",
+  "public-wifi",
+  "recycling-centres",
+  "road-events",
+  "sharing",
+  "solar",
+  "solar-roofs",
+  "station-arrivals",
+  "station-departures",
+  "station-facilities",
+  "stations",
+  "tax-rates",
+  "tourism",
+  "traffic",
+  "transit",
+  "tree-cadastre",
+  "unemployment",
+  "vehicle-registrations",
+  "water-level",
+  "weather",
+  "weather-warnings",
+  "webcams"
+]
  2. 49 tool updatesv1.0.1
    • Removedaccidents
    • Changedair_quality12 fields changed
      • removedInput schema / properties / slug / title
        Removed value: -"Slug"
      • removedInput schema / title
        Removed value: -"air_qualityArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Removedair_quality_live
    • Removedbusiness_registrations
    • Removedcharging
    • Changedcompare14 fields changed
      • removedInput schema / properties / cities / title
        Removed value: -"Cities"
      • changedInput schema / properties / resource / description
        Previous value: -"Resource to compare. Currently supported: 'weather' (DWD) or 'air' (UBA air quality)."New value: +"Resource to compare. Supported: 'weather' (DWD), 'air' (UBA air quality), 'indicators' (INKAR socioeconomic indicators incl. unemployment rate and EV charging coverage), 'demographics', 'unemployment', 'tourism', 'charging-status' (live EV charging occupancy, aggregates only) and 'weather-warnings' (official DWD warning level per city)."
      • removedInput schema / properties / resource / title
        Removed value: -"Resource"
      • removedInput schema / title
        Removed value: -"compareArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Removedconstruction
    • Removeddemographics
    • Removedelection
    • Removedenergy
    • Removedevents
    • Removedflood
    • Removedfuel_prices
    • Removedgeo
    • Changedget_city12 fields changed
      • removedInput schema / properties / slug / title
        Removed value: -"Slug"
      • removedInput schema / title
        Removed value: -"get_cityArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Changedget_city_overview12 fields changed
      • removedInput schema / properties / slug / title
        Removed value: -"Slug"
      • removedInput schema / title
        Removed value: -"get_city_overviewArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Addedget_city_resource
    • Removedhealth
    • Removedholidays
    • Removedicu_live
    • Removedindicators
    • Removedland_values
    • Changedlist_cities11 fields changed
      • removedInput schema / title
        Removed value: -"list_citiesArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Removedparking
    • Changedpois13 fields changed
      • removedInput schema / properties / slug / title
        Removed value: -"Slug"
      • removedInput schema / properties / type / title
        Removed value: -"Type"
      • removedInput schema / title
        Removed value: -"poisArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Removedpollen_uv
    • Removedpower_load
    • Removedpower_price
    • Removedroad_events
    • Removedsharing
    • Removedsolar
    • Removedsolar_roofs
    • Changedsources11 fields changed
      • removedInput schema / title
        Removed value: -"sourcesArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Removedstation_arrivals
    • Changedstation_board_arrivals13 fields changed
      • changedInput schema / properties / eva / description
        Previous value: -"Station EVA number (digits only) from the stations tool, e.g. '8000105' (Frankfurt Hbf)."New value: +"Station EVA number (digits only) from get_city_resource(slug, resource='stations'), e.g. '8000105' (Frankfurt Hbf)."
      • removedInput schema / properties / eva / title
        Removed value: -"Eva"
      • removedInput schema / title
        Removed value: -"station_board_arrivalsArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Changedstation_board_departures13 fields changed
      • changedInput schema / properties / eva / description
        Previous value: -"Station EVA number (digits only) from the stations tool, e.g. '8011160' (Berlin Hbf)."New value: +"Station EVA number (digits only) from get_city_resource(slug, resource='stations'), e.g. '8011160' (Berlin Hbf)."
      • removedInput schema / properties / eva / title
        Removed value: -"Eva"
      • removedInput schema / title
        Removed value: -"station_board_departuresArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Removedstation_departures
    • Removedstations
    • Removedtax_rates
    • Removedtourism
    • Removedtraffic
    • Removedtransit
    • Changedtransit_departures14 fields changed
      • removedInput schema / properties / slug / title
        Removed value: -"Slug"
      • changedInput schema / properties / stop_id / description
        Previous value: -"Optional stop ID; omit it to get the city's available departures."New value: +"Required stop ID to fetch departures for. Discover a city's stop IDs with get_city_resource(slug, resource='transit') first (each stop carries its id). Format: DELFI 'de:<AGS>:<id>' or a numeric gtfs.de stop id."
      • removedInput schema / properties / stop_id / title
        Removed value: -"Stop Id"
      • removedInput schema / title
        Removed value: -"transit_departuresArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Removedunemployment
    • Removedvehicle_registrations
    • Removedwater_level
    • Changedweather12 fields changed
      • removedInput schema / properties / slug / title
        Removed value: -"Slug"
      • removedInput schema / title
        Removed value: -"weatherArguments"
      • removedOutput schema / $defs / ToolMeta / description
        Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
      • removedOutput schema / $defs / ToolMeta / properties / attribution / title
        Removed value: -"Attribution"
      • removedOutput schema / $defs / ToolMeta / properties / cache_status / title
        Removed value: -"Cache Status"
      • removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
        Removed value: -"Correlation Id"
      • removedOutput schema / $defs / ToolMeta / properties / license / title
        Removed value: -"License"
      • removedOutput schema / $defs / ToolMeta / properties / source / title
        Removed value: -"Source"
      • removedOutput schema / $defs / ToolMeta / properties / source_status / title
        Removed value: -"Source Status"
      • removedOutput schema / $defs / ToolMeta / title
        Removed value: -"ToolMeta"
      • removedOutput schema / properties / data / title
        Removed value: -"Data"
      • removedOutput schema / title
        Removed value: -"ToolEnvelope"
    • Removedweather_warnings
    • Removedwebcams
  3. 48 tool updates
    • Changedaccidents2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedair_quality2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedair_quality_live2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Addedbusiness_registrations
    • Changedcharging2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedcompare3 fields changed
      • addedInput schema / properties / cities / description
        Added value: +"Comma-separated list of city slugs, e.g. 'berlin,koeln,hamburg' (max. 28 cities)."
      • addedInput schema / properties / resource / description
        Added value: +"Resource to compare. Currently supported: 'weather' (DWD) or 'air' (UBA air quality)."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedconstruction2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changeddemographics2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedelection2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedenergy2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedevents2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedflood2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedfuel_prices2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedgeo2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedget_city2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Addedget_city_overview
    • Changedhealth2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedholidays2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedicu_live2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedindicators2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Addedland_values
    • Changedlist_cities1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Addedparking
    • Changedpois3 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • addedInput schema / properties / type / description
        Added value: +"POI type from the API allowlist, one of: hospital, school, pharmacy, restaurant, police, kindergarten."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedpollen_uv2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedpower_load2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedpower_price2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedroad_events2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedsharing2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Addedsolar
    • Addedsolar_roofs
    • Changedsources1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedstation_arrivals2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Addedstation_board_arrivals
    • Addedstation_board_departures
    • Changedstation_departures2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Addedstations
    • Addedtax_rates
    • Changedtourism2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedtraffic2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedtransit2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedtransit_departures3 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • addedInput schema / properties / stop_id / description
        Added value: +"Optional stop ID; omit it to get the city's available departures."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedunemployment2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedvehicle_registrations2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedwater_level2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedweather2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedweather_warnings2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
    • Changedwebcams2 fields changed
      • addedInput schema / properties / slug / description
        Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}
  4. 38 tool updatesv1.0.0
    • First observedaccidents
    • First observedair_quality
    • First observedair_quality_live
    • First observedcharging
    • First observedcompare
    • First observedconstruction
    • First observeddemographics
    • First observedelection
    • First observedenergy
    • First observedevents
    • First observedflood
    • First observedfuel_prices
    • First observedgeo
    • First observedget_city
    • First observedhealth
    • First observedholidays
    • First observedicu_live
    • First observedindicators
    • First observedlist_cities
    • First observedpois
    • First observedpollen_uv
    • First observedpower_load
    • First observedpower_price
    • First observedroad_events
    • First observedsharing
    • First observedsources
    • First observedstation_arrivals
    • First observedstation_departures
    • First observedtourism
    • First observedtraffic
    • First observedtransit
    • First observedtransit_departures
    • First observedunemployment
    • First observedvehicle_registrations
    • First observedwater_level
    • First observedweather
    • First observedweather_warnings
    • First observedwebcams
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: general queries (get_city_overview, get_city, list_cities), specific data types (weather, air_quality, pois, transit_departures, station_board_departures/arrivals), comparisons (compare), source metadata (sources), and the generic accessor (get_city_resource). No overlap causes confusion.

Naming Consistency5/5

All tool names use lowercase with underscores, following a verb_noun pattern (e.g., get_city, list_cities, station_board_departures). Even single-word names like weather and pois are consistent with the style and clearly indicate their function.

Tool Count5/5

With 12 tools, the server is well-scoped for a city data API. It provides high-level discovery tools, specific data accessors for common queries, and a generic accessor for the full breadth of 65 data types. No unnecessary tools nor missing essential ones.

Completeness5/5

The tool surface covers the full lifecycle of data access: discovery (list_cities, get_city_overview, sources), base information (get_city), specific live data (weather, air_quality, transit, trains, POIs), and comparison. The generic get_city_resource fills any gaps, and no obvious missing operations are evident.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • germany-mcp-server

    AiAgentKarl
    A
    license
    B
    quality
    D
    maintenance
    MCP server providing AI agents with access to German government open data. 12 tools across 6 categories: Autobahn traffic, DWD weather, NINA disaster warnings, SMARD energy market, Bundestag parliamentary data, and pollen forecasts. All APIs are free, no keys required.
    16
    2
    MIT

  • dwd-mcp

    difu
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables access to German weather data from the Deutscher Wetterdienst, including station observations, forecasts, and warnings, through standardized MCP tools.
    MIT

  • mcp-govdata-de

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for GovData.de, Germany's national open-data portal via CKAN API, enabling AI agents to list publishing organizations and thematic groups.
    15
    MIT

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/street1983nk/infranode'

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