Skip to main content
Glama

Identify federal map layers at a point

identify_map_layers
Read-only

Query Swiss federal geodata layers at a WGS84 point and return raw feature attributes, enabling location-based checks for hazards, noise, zoning, and other mapped data.

Instructions

Power tool: query any federal geodata layer(s) at a WGS84 point (e.g. 'ch.bafu.laerm-strassenlaerm_tag' for road noise, 'ch.bafu.gefahren-basiskarte' hazards, 'ch.are.bauzonen' building zones). Returns raw attributes per matching feature.

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": {
      "lat": "<lat>",
      "lon": "<lon>",
      "layers": "<layers>"
    },
    "name": "identify_map_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude (Switzerland: ~45.8–47.9)
lonYesWGS84 longitude (Switzerland: ~5.9–10.6)
layersYesComma-separated geo.admin.ch layer IDs (BOD IDs), e.g. 'ch.bafu.laerm-strassenlaerm_tag'
toleranceNoSearch tolerance in metres

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, and the description adds that it returns raw attributes per matching feature. It does not cover no-match behavior, multi-layer result shape, or external-service constraints, leaving useful behavioral context unstated.

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?

The description is compact and front-loads the core operation before giving examples. 'Power tool' is slightly vague, but the examples earn their space by showing valid layer identifiers.

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?

With rich schema coverage and annotations, the definition is mostly complete: it states the operation, coordinate system, layer-ID form, and return content. The main gap is the absence of routing guidance versus similar layer-query tools.

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 lat, lon, layers, and tolerance with ranges and examples. The description reinforces the WGS84 point and layer-ID format but adds little meaning beyond the structured parameter definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: query federal geodata layer(s) at a WGS84 point, with concrete layer-ID examples. It is clear what the tool does, but it does not explicitly distinguish itself from similar siblings such as query_layer_at_point or search_map_layers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Power tool' and the layer-ID examples imply when this tool is appropriate, but there is no explicit when-to-use or when-not-to-use guidance. It never names an alternative tool or explains how it differs from nearby layer-querying siblings.

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