Skip to main content
Glama

Get Opendatasoft dataset schema & licence

get_portal_dataset
Read-only

Fetch schema and metadata for a Swiss Opendatasoft dataset to identify field names, types, record counts, and geo fields before querying its records.

Instructions

Schema and metadata of one dataset on a Swiss Opendatasoft portal (SBB, Basel, St. Gallen, Thurgau…): fields (name, label, type, description, facet), record count, licence, publisher, attributions, themes, last modified, and the geo_point field usable for radius search. Call this before query_portal_records to learn field names for where/select/order_by. Example: {portal:'sbb', dataset_id:'passagierfrequenz'}.

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": {
      "portal": "<portal>",
      "dataset_id": "<dataset_id>"
    },
    "name": "get_portal_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
portalYesPortal id, alias or domain: 'sbb' (data.sbb.ch), 'basel-stadt' (data.bs.ch), 'basel-landschaft' (data.bl.ch), 'st-gallen' (daten.sg.ch), 'stadt-st-gallen' (daten.stadt.sg.ch), 'graubuenden' (data.gr.ch), 'thurgau' (data.tg.ch); any other '<tenant>.opendatasoft.com' host also works
dataset_idYesDataset id from search_portal_datasets, e.g. 'passagierfrequenz' (SBB) or '100088' (Basel-Stadt ids are numeric)

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 safety profile is covered; the description still adds real context by enumerating what comes back and pointing out the geo_point field usable for radius search. It says nothing about failure modes (unknown portal or dataset id, unknown tenants), which keeps it short of 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 the resource and return contents, then the call-to-action, then a compact example. The metadata enumeration is long but each item is informative; there is no filler, though the single 40-word sentence is dense.

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?

For a read-only two-parameter lookup with no output schema, the description covers purpose, return shape, and its role in the query workflow, which is what an agent needs. The remaining gap is the unresolved overlap with get_dataset/describe_dataset_columns and no note on behavior for invalid portal or dataset ids.

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 description coverage is 100% and the schema already lists the portal aliases and dataset_id format, so the description's example object ({portal:'sbb', dataset_id:'passagierfrequenz'}) largely restates structured data. The baseline of 3 applies because the schema, not the description, carries parameter meaning.

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?

States a concrete resource and scope: 'Schema and metadata of one dataset on a Swiss Opendatasoft portal', and enumerates the returned surface (fields, record count, licence, publisher, themes, last modified, geo_point). An agent can distinguish it from query_portal_records. It does not, however, differentiate itself from similarly named siblings such as get_dataset or describe_dataset_columns, whose overlap is left for the agent to guess.

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 explicit sequencing guidance: 'Call this before query_portal_records to learn field names for where/select/order_by', which names the alternative and the condition that selects it. It offers no exclusion for the look-alike siblings (get_dataset, describe_dataset_columns), so the guidance is clear but not exhaustive.

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