Skip to main content
Glama

swiss-living-index

Read a dataset

get_dataset
Read-onlyIdempotent

Read one Swiss Living Index dataset (id from list_datasets), exactly as published on the site (official values, unchanged). Filter with canton (2-letter) and/or commune (name or BFS number), section (a top-level key), from_year / to_year. Large datasets return a size summary first so you can narrow the request. Every reply carries source, source URL and the page to cite.

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 from list_datasets, e.g. "migration/migration-switzerland".
cantonNoCanton as 2-letter abbreviation, e.g. "ZH", "GE", "TI". Filters the dataset to that canton.
max_kbNoreply size limit in KB, default 150, max 600
communeNoSwiss commune: official name, BFS number or 4-digit postcode, e.g. "Winterthur", "230" or "8400". «8001 Zürich» and «Basel (BS)» also work. Filters the dataset to that commune.
sectionNoOne top-level section of the dataset (the too_large answer lists them).
to_yearNoKeep year series up to this year, e.g. 2025.
from_yearNoKeep year series from this year, e.g. 2015.

Output Schema

NameRequiredDescriptionDefault
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / canton / description
      Added value: +"Canton as 2-letter abbreviation, e.g. \"ZH\", \"GE\", \"TI\". Filters the dataset to that canton."
    • addedInput schema / properties / commune / description
      Added value: +"Swiss commune: official name, BFS number or 4-digit postcode, e.g. \"Winterthur\", \"230\" or \"8400\". «8001 Zürich» and «Basel (BS)» also work. Filters the dataset to that commune."
    • addedInput schema / properties / from_year / description
      Added value: +"Keep year series from this year, e.g. 2015."
    • addedInput schema / properties / id / description
      Added value: +"Dataset id from list_datasets, e.g. \"migration/migration-switzerland\"."
    • addedInput schema / properties / section / description
      Added value: +"One top-level section of the dataset (the too_large answer lists them)."
    • addedInput schema / properties / to_year / description
      Added value: +"Keep year series up to this year, e.g. 2025."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "attribution": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-open-world), and the description adds real behavioral context beyond them: values are unmodified official figures, oversized datasets return a size summary instead of the full payload, and every reply includes source, source URL and citation page. It does not state what happens on an invalid id or a filter that matches nothing.

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?

Three sentences, front-loaded with the read action and the filter list, with no filler. The middle sentence packs four filters into a dense clause, which reads slightly list-like but every element carries operational meaning.

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 an output schema present, return values need no explanation, and the description covers the id source, the filtering model, size-limit behavior and provenance. The only gaps are failure modes (unknown id, empty filter result), which are minor for a read-only fetch.

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 seven parameters are already documented, including canton as a 2-letter code and commune accepting name, BFS number or postcode. The description restates the filter set and ties section to the too_large answer, but adds little syntax or behavior beyond the schema; baseline 3 applies.

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?

"Read one Swiss Living Index dataset (id from list_datasets)" states a specific verb and resource and explicitly points to the sibling that supplies the id, so it is distinguishable from list_datasets and from metric-level tools like rank_by_metric or get_trend. The parenthetical also bounds the return to data exactly as published.

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 gives clear operating context: obtain the id from list_datasets, narrow with canton/commune/section/year filters, and rely on the size summary when a dataset is large. It stops short of saying when to choose this over siblings such as get_trend or compare_cantons, so the routing guidance is implicit rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources