Skip to main content
Glama

Query up to 15 geo.admin.ch layers at a point, radius or bbox

query_layer_at_point
Read-only

Read attributes of Swiss federal map layers at a WGS84 point, within a radius, or inside a bbox; query up to 15 layers per call, with results grouped by layer.

Instructions

Read the attributes of any federal map layers at a WGS84 location: point-in-polygon (radius_m=0), everything within a radius in metres (e.g. antennas within 300 m), or everything inside a bbox. Up to 15 layers per call; results grouped per layer, with per-layer errors isolated if a layer id is bad. Examples: layers='ch.bafu.laerm-strassenlaerm_tag,ch.bag.radonkarte', lat=46.948, lon=7.4474; layers='ch.bakom.standorte-mobilfunkanlagen', radius_m=300, return_geometry=true. Use search_map_layers to find layer ids; for a ready-made multi-layer summary use get_location_report.

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": {
      "layers": "<layers>"
    },
    "name": "query_layer_at_point"
  }
}

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)
bboxNoAlternative to lat/lon: WGS84 bbox [minLon,minLat,maxLon,maxLat], max ~5 km per side
langNoLanguage for labels/attributes: de, fr, it, rm or en (default en)en
layersYesComma-separated layer ids (max 15), e.g. 'ch.bafu.laerm-strassenlaerm_tag,ch.are.bauzonen'
radius_mNoSearch radius in metres around lat/lon (0 = exactly at the point; max 2000)
time_instantNoYear for time-enabled layers (see get_layer_info)
per_layer_limitNoMax features returned per layer (default 5)
return_geometryNoInclude a WGS84 anchor point per feature (useful with radius/bbox)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavior: the 15-layer ceiling, results grouped per layer, and per-layer error isolation when a layer id is invalid. It does not discuss rate limits, truncation when per_layer_limit is hit, or what an empty result looks like, which keeps it short of a 5.

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-loaded with the core verb and modes, then examples, then sibling routing — a sensible order with no filler. The opening sentence is long and packs several clauses together, which slightly slows scanning, but every sentence carries information.

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 9-parameter tool with no output schema, the description covers input modes, limits, result grouping, and partial-failure behavior, which is close to what an agent needs. It stops short of describing the per-feature payload shape or how bbox and lat/lon precedence is resolved if both are supplied.

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, but the description earns a bump by showing two full parameter combinations that demonstrate the intended interaction between layers, lat/lon, radius_m, and return_geometry. Those examples convey how parameters compose in a way the flat property descriptions do not.

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?

States a specific verb-plus-resource (read attributes of federal map layers) and enumerates the three spatial modes it supports: point-in-polygon, radius in metres, and bbox. The 15-layer cap and per-layer grouping further pin down exactly what the call returns, so an agent can distinguish it from feature-lookup siblings.

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 routes the agent: use search_map_layers to obtain layer ids, and get_location_report for a ready-made multi-layer summary. It also tells the agent which spatial mode corresponds to which intent (radius_m=0 for a single point, radius_m=300 for nearby antennas, bbox for an area), including a concrete example for each.

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