Skip to main content
Glama

Get dataset details & download links

get_dataset
Read-only

Fetch complete metadata for one Swiss open-data dataset by ID, including description, publisher, licence, resource formats, queryability and direct download links.

Instructions

Full metadata for one dataset on opendata.swiss (or portal='stadt-zuerich'): description, publisher, licence and every resource with its 0-based index, format, whether it is queryable by query_dataset, and its direct download link.

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": {
      "id": "<id>"
    },
    "name": "get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDataset ID (slug) from search_datasets
langNoLanguage for titles/descriptions: de, fr, it or en (default en; falls back to de)
portalNoCatalogue: 'opendata.swiss' (default, national), 'stadt-zuerich' (City of Zürich, data.stadt-zuerich.ch) or 'envidat' (WSL/ETH environmental research data: snow, glaciers, forests, biodiversity, climate)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real value by disclosing the shape of the payload (per-resource 0-based index, format, queryable flag, direct download link) which is essential because there is no output schema. It does not mention error behavior for unknown IDs/slugs or any rate/size limits, so it is strong but not exhaustive.

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?

It is a single front-loaded sentence that leads with the core purpose before enumerating return fields, and every clause carries information. It is dense and long, but no sentence is wasted padding; a light structural break would improve scanability.

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 the return payload and does so concretely, including the resource index needed for downstream query_dataset calls. Given three fully documented parameters and read-only annotations, the remaining gap is only around failure modes and payload size, which is a minor omission for a metadata lookup tool.

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%, so all three parameters are already documented, including enum values and the language fallback to 'de'. The description mostly restates this, and notably mentions only opendata.swiss and stadt-zuerich while the schema also defines 'envidat', so it adds no meaning beyond the schema and is slightly narrower than it.

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 verb+resource ('full metadata for one dataset') and then enumerates exactly what that metadata contains (description, publisher, licence, resources with index, format, queryability, download link). It also names the catalogue scope and references siblings (search_datasets for the ID, query_dataset for the queryable flag), so an agent can distinguish it from the search and query tools without opening a 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?

Usage context is clear: call this once you have a dataset slug from search_datasets and need complete detail plus download links, and the portal parameter switches catalogues. What is missing is an explicit 'do not use this to fetch rows' exclusion or guidance against describe_dataset_columns for column-level needs; the agent must infer that from the mention of query_dataset.

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