InfraNode

City Base Data

get_city

Read-onlyIdempotent

Look up base data for a German city including population, area, and coordinates. Confirms city existence and provides core attributes from Wikidata.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_city"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'.

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.0.1Jul 6, 2026
- 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"
```

Changed2 schema fields changedJun 25, 2026

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"
+}

First observedv1.0.0Jun 18, 2026

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.

Deploy Server