Skip to main content
Glama

InfraNode

by dev.infranode

Compare Cities

compare
Read-onlyIdempotent

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.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaYes

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds valuable context by explaining the per-city source_status handling (e.g., no_data, error) and that missing sources don't spoil the answer, but it doesn't detail any other behavioral aspects like rate limits or response structure beyond the output schema.

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, with a clear opening line that summarizes the core function, followed by two sentences that explain the fan-out behavior and resilience. No redundant information; every sentence adds value, and the structure 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?

With a high-confidence schema (100% coverage), rich annotations (read-only, idempotent, non-destructive), and an output schema, the description completes the picture by clarifying the per-city status handling and scope. It's fully adequate for an agent to decide when and how to use this tool versus alternatives.

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 the schema already documents both parameters with examples (e.g., city slugs, supported resources). The description reinforces the meaning of 'resource' by listing supported values, but since the schema already provides this, the additional value is limited, aligning with 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 states the tool compares ONE resource across MULTIPLE cities, distinguishing it from single-city tools like get_city_resource or weather. It specifies the output format (per-city source_status) and explicitly notes read-only behavior, making the purpose unambiguous and distinct from siblings.

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 usage for comparing a resource across cities and notes that it fans out over listed cities, preventing one failing city from spoiling the result. It doesn't explicitly state when not to use it or name alternatives, but the mission from siblings (e.g., get_city_resource for single-city) is clear, and the 'read-only' note discourages misuse for mutable operations.

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

All InfraNode toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation3/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Resources