Skip to main content
Glama

List Swiss Opendatasoft data portals

list_data_portals
Read-only

Lists Swiss Opendatasoft open-data portals and what each covers, helping you choose the right portal before searching datasets or querying records.

Instructions

Registry of Swiss open-data portals that run on Opendatasoft and can be searched/queried with search_portal_datasets, get_portal_dataset and query_portal_records: SBB (data.sbb.ch: station passenger frequency, rolling stock, actual train times), Basel-Stadt (real-time parking, Rhine temperature, air quality, elections), Basel-Landschaft, Canton & City of St. Gallen, Graubünden, Thurgau. Returns id, name, operator, domain, licence note, platform confidence and what each portal is good for.

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": "list_data_portals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by enumerating the returned fields (id, name, operator, domain, licence note, platform confidence, what each portal is good for) and by characterizing each portal's content, but it says nothing about whether the registry is static or live, how current the licence/confidence metadata is, or how large the result set is.

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 the core definition, then the downstream tools, then the return fields. The parenthetical portal inventory (SBB, Basel-Stadt, etc.) is long but earns its place by letting an agent judge coverage before calling. Slightly dense as a single run-on sentence, but no filler.

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, the description carries the burden of describing return values and does so explicitly. For a zero-parameter read-only listing tool this is close to complete; only the freshness/authority of the registry metadata is left unstated.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description needs to compensate for. The description correctly spends its space on scope and return content instead of inventing parameter guidance.

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 resource (Swiss open-data portals running on Opendatasoft) with a clear scope qualifier, and explicitly names the three sibling tools that consume the result (search_portal_datasets, get_portal_dataset, query_portal_records). An agent can distinguish this discovery tool from the query tools 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the usage context clear by tying the listed portals to the three tools that search/query them, implying this is the entry point for portal discovery. It stops short of an explicit 'call this first when you don't know the portal id' instruction or any when-not guidance, so it is strong but not fully prescriptive.

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