Skip to main content
Glama

Search datasets on Swiss Opendatasoft portals

search_portal_datasets
Read-only

Search Swiss SBB and cantonal or city Opendatasoft dataset catalogues by keyword to find datasets, record counts, themes and last-modified dates. Search one portal or all in parallel.

Instructions

Full-text search of dataset catalogues on SBB and cantonal/city Opendatasoft portals; one portal or all in parallel (per-portal errors are reported, not fatal). Returns portal, dataset_id, title, short description, record count, last-modified date and themes; pass portal + dataset_id to get_portal_dataset / query_portal_records. Examples: {query:'passagierfrequenz', portal:'sbb'} (passengers per station), {query:'rollmaterial', portal:'sbb'}, {query:'Parkhaus'} (real-time parking), {query:'Rhein Temperatur', portal:'basel-stadt'}, {query:'Wahlen'}. Metadata is mostly German: use German terms. Omit query (with a portal) to list its most recently modified datasets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_portal_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results per portal (capped at 15 when searching all portals)
queryNoSearch terms, e.g. 'Parkhaus', 'Luftqualität', 'Haltestellen', 'Bevölkerung'
portalNoOptional portal (id/alias/domain). Omit to search all registered portals in parallel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses that all-portal searching runs in parallel and that per-portal errors are reported rather than fatal. It also enumerates the returned fields and the German-language metadata constraint, which is exactly the kind of context annotations cannot convey.

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?

Core behavior and return shape are front-loaded, followed by examples and a language note. The five examples are more than strictly necessary but each demonstrates a distinct portal/query pattern, so the length is mostly earned.

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 no output schema, the description compensates by listing all returned fields, and it covers parallel execution, error tolerance, follow-up tools, and query-language expectations. An agent has everything needed to invoke it correctly and chain the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema lacks: omitting query with a portal switches the tool into a recent-datasets listing mode, and portal accepts an id/alias/domain or omission for all portals. The limit capping is already in the schema, so only partial extra value.

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 names a specific verb (full-text search) and a specific resource (dataset catalogues on SBB and cantonal/city Opendatasoft portals), and it scopes the tool to one portal or all in parallel. An agent can distinguish it from a generic catalog search sibling without opening the schema.

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 states concrete routing rules — pass portal + dataset_id onward to get_portal_dataset / query_portal_records, and omit query with a portal to list recently modified datasets. It also warns that metadata is mostly German so German terms should be used. It does not explicitly say when to prefer a different search sibling, which keeps it from a 5.

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