Skip to main content
Glama

Search the federal data catalogue (I14Y)

search_federal_metadata
Read-only

Search Switzerland's I14Y platform for federal, cantonal, and municipal datasets, APIs, public services, and code lists. Find which authority holds specific data or an official code list ID.

Instructions

Search I14Y, the Swiss federal interoperability platform: datasets (incl. non-public registers, with their access rights), data services/APIs, public services and concepts/code lists from federal, cantonal and municipal bodies. Use it to find which authority holds what data, or the identifier of an official code list. Example: {query: 'NOGA', types: ['Concept']}, {query: 'Gebäude', types: ['Dataset']}.

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_federal_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
limitNo
queryYes
typesNoRestrict to Dataset, DataService, Concept (incl. code lists), PublicService, MappingTable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description only needs to add context, and it does: it discloses that non-public registers are included and carry access-rights information, which the agent would not know otherwise. Gaps remain around pagination, result-size behaviour, and ranking, but nothing contradicts the annotations.

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?

Two compact sentences plus a short example list, with the platform identity and scope front-loaded before the use cases. The examples earn their place by showing syntax, though the parenthetical about non-public registers is slightly crammed into the opening sentence.

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 no output schema and only four parameters, the definition would need to hint at what comes back; it does so partially by framing results as authority ownership and code-list identifiers. It is complete enough to call correctly, with the main residual gap being return-shape and result-volume expectations for an open-world search.

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 only 25%, so the description should carry more weight than it does. It effectively explains `types` by listing the five categories and illustrates `query` semantics via real examples ('NOGA', 'Gebäude'), but `lang` and `limit` receive no attention at all, leaving a real coverage gap.

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?

Names a specific verb and resource (search I14Y) and enumerates the entity types covered — datasets, data services, public services, concepts/code lists — plus the geographic scope (federal, cantonal, municipal). It identifies the platform by name, which implicitly separates it from siblings such as search_library_catalogue or search_federal_gazette, but never states the contrast explicitly.

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?

Gives two concrete use cases — finding which authority holds a dataset, and resolving an official code-list identifier — with worked examples showing query/type combinations. It stops short of stating when NOT to use it or which sibling to pick instead (e.g. search_datasets, search_cpv_codes), so alternatives are left to inference.

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