Skip to main content
Glama

Get a geo.admin.ch layer's fields and metadata

get_layer_info
Read-only

Retrieve geo.admin.ch layer details—title, abstract, owner, queryability, time support, attribute fields, sample values, and legend/map links—to choose search fields or interpret point-query results.

Instructions

Describe one geo.admin.ch layer: title, abstract, data owner, whether it is queryable (identify/find work), time-enabled, attribute fields (name/alias/type + sample values) and legend/map links. Use before find_layer_features (to pick a search field) or to interpret query_layer_at_point attributes. Example: layer_id='ch.bag.radonkarte'.

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>"
    },
    "name": "get_layer_info"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the bar is lower, and the description still adds real context by disclosing the return payload surface (metadata plus sample attribute values) that the agent otherwise could not anticipate, since there is no output schema. It does not mention whether unknown layer_ids error or return empty, or any rate/pagination behavior, which is the remaining gap.

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?

It is front-loaded with the core purpose, followed by usage guidance and then a concrete example, with no filler sentences. The long enumeration of returned fields makes the opening sentence run on, but each item earns its place because no output schema exists to carry that information.

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 only two simple parameters, no nested objects and no output schema, the description carries the return-shape burden well by listing the fields returned. Combined with the sequencing guidance relative to find_layer_features and query_layer_at_point, an agent has enough to call this 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%, with both layer_id (pattern, example, how to find ids) and lang (enum of five values, default en) fully documented in the schema itself. The description only adds a redundant example layer_id value, so the baseline 3 applies.

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 opens with a specific verb and resource ('Describe one geo.admin.ch layer') and then enumerates exactly what is described: title, abstract, data owner, queryability, time-enablement, attribute fields with sample values, and legend/map links. It also names the sibling tools it relates to, so an agent can separate it from find_layer_features and query_layer_at_point without opening any schema.

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?

It gives explicit sequencing guidance: 'Use before find_layer_features (to pick a search field)' and 'to interpret query_layer_at_point attributes'. Both the alternative tools and the conditions that select them are stated rather than inferred, which leaves little ambiguity about when to reach for this tool.

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