Skip to main content
Glama

Get geo.admin.ch feature(s) by id

get_layer_feature
Read-only

Fetches full attributes for up to 10 geo.admin.ch layer features by feature ID; use IDs from point queries or layer searches to inspect specific map objects.

Instructions

Fetch the full attributes of one or more features of a geo.admin.ch layer by feature id (ids come from query_layer_at_point or find_layer_features). Example: layer_id='ch.bfs.gebaeude_wohnungs_register', feature_id='1231641_0'. Up to 10 comma-separated ids.

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": {
      "layer_id": "<layer_id>",
      "feature_id": "<feature_id>"
    },
    "name": "get_layer_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for labels/attributes: de, fr, it, rm or en (default en)en
layer_idYesgeo.admin.ch layer id (BOD id), e.g. 'ch.bafu.laerm-strassenlaerm_tag', find ids with search_map_layers
feature_idYesFeature id, or up to 10 comma-separated ids
return_geometryNoInclude a WGS84 anchor point

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/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 and external-data profile is covered. The description adds useful operational detail (10-id batch cap, WGS84 anchor via return_geometry, language affecting labels/attributes) but says nothing about failure modes for invalid ids, partial results in a batch, or response size for 'full attributes'. With annotations doing the heavy lifting, this is adequate but not rich.

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?

Three short sentences, front-loaded with the core action, followed by id provenance and the batch constraint. The inline example is dense with usable information and nothing is redundant filler.

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 read-only lookup with no output schema, the description conveys what comes back ('full attributes', optional geometry anchor) and the batch shape. It would be stronger with a note on what happens when an id resolves to nothing, but an agent has enough to call it correctly.

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 all four parameters are already documented in the schema, including the 10-id limit and the WGS84 anchor. The description contributes a concrete worked example (layer_id plus feature_id), which helps with id format, but largely restates what the schema provides. Baseline 3 is appropriate here.

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 opens with a specific verb and resource ('Fetch the full attributes of one or more features of a geo.admin.ch layer by feature id'), which is unambiguous and distinct from search-type siblings. It also signals that this is a retrieval-by-identifier tool rather than a discovery tool by naming where ids originate, though it never explicitly contrasts itself with find_layer_features.

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 gives clear context for when this tool applies: you must already have a feature id, sourced from query_layer_at_point or find_layer_features. That is a real routing hint, and the batch limit ('up to 10 comma-separated ids') sets expectations. It lacks an explicit when-not or a statement about what to do if ids are unknown beyond the two named sources.

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