Skip to main content
Glama

Search the geo.admin.ch map layer catalogue

search_map_layers
Read-only

Find Swiss federal map layers by keyword; returns matching layer IDs and titles for metadata lookup or point queries.

Instructions

Full-text search over the ~900 federal map layers on geo.admin.ch (noise, natural hazards, radon, zoning, protected areas, energy, transport, geology, …). Returns layer ids (e.g. 'ch.bafu.laerm-strassenlaerm_tag') with titles. Next: get_layer_info for fields/metadata, or query_layer_at_point to read values at a location. Examples: query='Strassenlärm', 'radon', 'Grundwasserschutz', 'solar', 'Bauzonen'.

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": {
      "query": "<query>"
    },
    "name": "search_map_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for labels/attributes: de, fr, it, rm or en (default en)en
limitNoMax layers (default 15, max 30)
queryYesKeywords (any national language or English), e.g. 'noise', 'Hochwasser', 'antennas'

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 and openWorldHint, and the description adds real context beyond them: catalogue size, the topical breadth searched, and the concrete return shape (layer ids such as 'ch.bafu.laerm-strassenlaerm_tag' with titles). It stops short of noting result-ranking or truncation behavior, which keeps it below 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 purpose and coverage, then next-steps, then examples — a sound order with no filler sentences. The example list is slightly redundant with the schema's own query examples, which keeps it from a perfect score.

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?

For a read-only search with no output schema, the description supplies everything the agent needs: what corpus is searched, what comes back (ids + titles), and which tools to call next. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so query, lang and limit are all documented in the schema, including the multilingual query hint. The description's examples restate that query flexibility rather than adding new semantics (e.g. matching behavior or whether ids are matched too), 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?

States a specific verb ('full-text search') and a precisely scoped resource ('~900 federal map layers on geo.admin.ch'), plus concrete topical coverage (noise, radon, zoning, geology…). An agent can tell this apart from get_layer_info or 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?

Explicitly routes to alternatives by naming the follow-up conditions: 'Next: get_layer_info for fields/metadata, or query_layer_at_point to read values at a location.' The example queries also show what kind of input this tool expects versus a metadata or point-query 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