Skip to main content
Glama

Opendata Swiss

by io.github.pipeworx-io
OverviewAdmin

Search Datasets

search_datasets
Read-onlyIdempotent

Search the opendata.swiss catalogue (CKAN package_search). Returns matching Swiss federal/cantonal datasets. Titles/descriptions are multilingual {de,fr,it,en}; each result is annotated with English-preferred title_en/notes_en.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqNoSolr filter query, e.g. "organization:bundesamt-fur-statistik-bfs" or "groups:health".
rowsNo1-1000 (default 25).
sortNoe.g. "metadata_modified desc", "score desc".
queryYesFree-text query, e.g. "energy", "population", "ÖV".
startNo0-based offset for paging.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "energy"
+  },
+  {
+    "fq": "organization:bundesamt-fur-statistik-bfs",
+    "query": "population",
+    "rows": 50,
+    "sort": "metadata_modified desc"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations (readOnly, idempotent, openWorld), the description discloses that titles/descriptions are multilingual and each result is annotated with English-preferred fields (title_en, notes_en), which is critical for correct interpretation.

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?

Two concise sentences: first states purpose and source, second adds crucial detail about multilingual results. No redundant information.

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?

No output schema exists, but the description partially compensates by detailing result fields (multilingual, English-preferred). Missing information on pagination or total result counts, but overall adequate.

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% with full parameter descriptions. The description does not add significant parameter-level meaning beyond the schema, resulting in a baseline score.

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 clearly states the tool searches the opendata.swiss catalogue using CKAN package_search, returning Swiss federal/cantonal datasets. This distinguishes it from siblings like search_within or dataset_details.

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?

The description provides clear context about the target catalogue (opendata.swiss) and dataset scope (Swiss federal/cantonal), but does not explicitly specify when to use this tool versus alternatives or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Opendata Swiss toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources