list_citiesList 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.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| meta | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / $defs / ToolMeta / properties / noteAdded value: +{
+ "type": "string"
+}Input schema / titleRemoved value: -"list_citiesArguments"Output schema / $defs / ToolMeta / descriptionRemoved 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."Output schema / $defs / ToolMeta / properties / attribution / titleRemoved value: -"Attribution"Output schema / $defs / ToolMeta / properties / cache_status / titleRemoved value: -"Cache Status"Output schema / $defs / ToolMeta / properties / correlation_id / titleRemoved value: -"Correlation Id"Output schema / $defs / ToolMeta / properties / license / titleRemoved value: -"License"Output schema / $defs / ToolMeta / properties / source / titleRemoved value: -"Source"Output schema / $defs / ToolMeta / properties / source_status / titleRemoved value: -"Source Status"Output schema / $defs / ToolMeta / titleRemoved value: -"ToolMeta"Output schema / properties / data / titleRemoved value: -"Data"Output schema / titleRemoved value: -"ToolEnvelope"Output 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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the behavioral trait that the tool returns slug, federal state, population, and coverage – context not in the annotations. It also states it takes no arguments, which matches the schema. The only minor gap is not explicitly confirming the return format (e.g., array of objects), but the output schema likely handles that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is four short sentences, each earning its place. The first sentence states purpose and output. The second and third sentences give usage guidance. The fourth confirms safety. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters, full annotation coverage, and a provided output schema, the description is complete. It tells the agent what the tool does, what it returns, how to use it (call first, no args), and why it's important (discovery for city-slug-dependent tools). No gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and there are zero parameters, so the baseline is 4. The description correctly confirms no arguments are needed, which adds value by reinforcing the schema's emptiness and explaining the tool's role in the workflow.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a clear verb ('List') and specifies the resource ('all covered cities'). It explicitly states the fields returned (slug, federal state, population, coverage), distinguishing it from sibling tools that likely operate on a single city (e.g., get_city) or require a city slug as input.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance: it takes no arguments and should be called first to discover valid city slugs before invoking any city-scoped tool. This clearly tells the agent when to use it (initial discovery) and for what purpose (obtaining slugs for subsequent tools), effectively differentiating it from all sibling tools that require a city parameter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there is potential confusion between 'get_city_resource' and specific resource accessors like 'weather', 'air_quality', 'transit_departures', 'station_board_arrivals', and 'station_board_departures'. The descriptions do clarify that some specific tools exist for convenience or source-specific details, but the boundary isn't always sharp. Also, 'compare' could overlap with using 'get_city_resource' repeatedly. An agent might hesitate between using the generic resource accessor and the named tool.
The naming convention is mostly consistent: verbs like 'get', 'list', 'compare', and 'pois' (abbreviation) are used. The pattern is generally 'verb_noun' (e.g., 'get_city', 'list_cities', 'station_board_arrivals'). Minor deviations include 'pois' being an acronym rather than a full verb phrase, and 'air_quality' vs 'weather' implying a noun rather than an action. But overall it's predictable and readable.
12 tools is a well-scoped count for a city data platform. The function set covers discovery (list_cities, sources), overview (get_city_overview), base data (get_city), specific data types (weather, air_quality, transit_departures, station_board_*, pois), a generic accessor (get_city_resource), and a comparison tool (compare). Each tool feels necessary and the set is not overwhelming.
The tool surface is quite comprehensive for a read-only city information server. It provides discovery (list_cities, get_city_overview), base data, and access to 81 data types via get_city_resource. The named tools cover the most common queries (weather, air quality, transit). A minor gap is the lack of a tool to aggregate or search across cities (though 'compare' helps). Editing or write operations are not expected here, but for read-only, it's nearly complete.