Skip to main content
Glama

City Data by Type

get_city_resource
Read-onlyIdempotent

Fetch any of 67 data types for a German city—live data, statistics, infrastructure—by providing the city slug and resource key.

Instructions

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.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaYes
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.

Install Server

Other Tools

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