Skip to main content
Glama

Federal geodata report for a Swiss address or point

get_location_report
Read-only

Geocode a Swiss address or coordinates and check ~20 federal layers—buildings, noise, hazards, heritage, energy—in one location due-diligence call.

Instructions

One-call location due-diligence: geocodes an address (or takes lat/lon) and queries ~20 curated federal layers in parallel, municipality & postcode, registered buildings (GWR), building zone, public-transport quality class, road & rail noise day/night, radon, surface-runoff flooding, seismic subsoil class, groundwater protection zones, contaminated sites, mobile antennas within 300 m, ISOS townscape, BLN landscape, roof solar suitability and district heating networks. Each layer reports status match/no_match/error independently. Examples: address='Bundesplatz 3, Bern'; lat=47.3769, lon=8.5417, topics=['noise','hazards'].

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_location_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoWGS84 latitude, e.g. 46.9480 (Switzerland ≈ 45.8–47.8)
lonNoWGS84 longitude, e.g. 7.4474 (Switzerland ≈ 5.9–10.5)
langNoLanguage for labels/attributes: de, fr, it, rm or en (default en)en
topicsNoRestrict to topics: admin, buildings, mobility, noise, hazards, environment, heritage, energy (default all)
addressNoSwiss address or place, e.g. 'Bahnhofstrasse 1, Zürich'
extra_layersNoUp to 5 additional comma-separated layer ids to include (point query)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description does add meaningful behavior beyond them: layers are queried in parallel and each reports match/no_match/error independently, which signals partial-failure semantics. It does not mention latency, rate limits, or what happens when geocoding fails.

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?

Purpose is front-loaded in the first clause before the layer enumeration, and the examples at the end are compact and usable. The layer list is long but earns its place by supporting tool selection; the single run-on sentence is dense rather than wasteful.

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?

For a six-parameter aggregator with no output schema, the description covers scope, input modes, filtering, and per-layer status reporting, which is most of what an agent needs. Gaps remain around input precedence (address vs lat/lon) and error/default behavior when a layer or geocode fails.

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 the baseline is 3; the description goes further by showing address and lat/lon are alternative input modes and by demonstrating a realistic topics filter value. It does not explain the interaction between topics and extra_layers or what happens when neither address nor coordinates are supplied.

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 names a specific verb and resource — 'geocodes an address (or takes lat/lon) and queries ~20 curated federal layers in parallel' — and then enumerates the concrete layer domains (GWR, building zone, noise, radon, seismic, ISOS, BLN, solar, district heating). This makes it clearly distinguishable from single-layer siblings like query_layer_at_point or get_building.

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?

It frames the tool as a 'one-call location due-diligence' aggregator and shows that topics narrows scope while extra_layers adds point-query layers, which tells an agent when this bulk call is appropriate. It stops short of explicitly saying when to prefer a cheaper sibling such as query_layer_at_point or get_building for a single layer.

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

Deploy Server

Other Tools