seco-labor-mcp

Overview Schema Source Related Servers Discussions Admin

Aktuelle Arbeitslosigkeit Schweiz

seco_get_unemployment_overview

Read-only

Retrieve Swiss annual unemployment overview: registered unemployed yearly averages from SECO/BFS data since 2000, with clear labeling to avoid confusion with ILO unemployment.

Instructions

Registrierte Arbeitslose der Schweiz — SECO-Zahlen, publiziert vom BFS.

Liefert die Jahresreihe der registrierten Arbeitslosen (Jahresdurchschnitt, 2000 bis heute) aus der BFS-Tabelle T3.3.0.1. Die Zahlen stammen aus SECOs RAV-System; das BFS veröffentlicht sie und nennt SECO als Quelle.

Was dieses Werkzeug nicht liefert: monatliche Werte und kantonale Aufschlüsselungen. Beide gibt es auf opendata.swiss nicht in maschinenlesbarer Form — geprüft am 2026-08-14 über den ganzen Bestand. Wer sie braucht, findet sie interaktiv auf amstat.ch. Eine Abfrage mit canton bekommt deshalb eine Absage und keine national aggregierte Zahl, die so aussieht, als wäre sie kantonal.

Nicht mit der ILO-Erwerbslosigkeit verwechseln. Dieselbe Tabelle führt beide Reihen; die ILO-Zahl lag im Jahr 2000 um 76 Prozent höher. Das Werkzeug gibt beide aus und beschriftet sie, statt sie zu vermischen.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes	Contains: - canton (Optional[str]): wird abgelehnt, siehe oben. - year (Optional[int]): Jahr der Reihe. None = jüngstes verfügbares. - response_format (str): 'markdown' oder 'json'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.0Sep 20, 2026

changedInput schema / properties / params / description

Previous value: -"Contains:\n- canton (Optional[str]): Canton code (e.g. 'ZH'). None = national.\n- year (Optional[int]): Filter year. None = latest available.\n- response_format (str): 'markdown' or 'json'"New value: +"Contains:\n- canton (Optional[str]): wird abgelehnt, siehe oben.\n- year (Optional[int]): Jahr der Reihe. None = jüngstes verfügbares.\n- response_format (str): 'markdown' oder 'json'"

First observedv0.3.0May 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely valuable behavior: a canton query is rejected with a refusal rather than a misleading national aggregate, and the tool outputs both SECO and ILO series labeled separately rather than mixing them. This contextualizes the data lineage (BFS publishes, SECO sources) beyond what structured fields 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?

Front-loaded with the core purpose, then exclusions, then the ILO caveat. Well-organized with bold section breaks. Slightly long but every section earns its place given the rejection behavior and dual-series nuance; no filler.

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 an output schema present and the complex canton-refusal behavior fully explained, nothing an agent needs to call this correctly is missing. Covers source, scope, exclusions, and the labeling of the two series.

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% — all three params are documented in the schema. The description adds real value by reinforcing that canton is rejected outright and that year=None returns the latest available data, which clarifies the intent behind the nullable types beyond what the schema states.

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 precisely what it delivers: the annual series of registered unemployed (yearly average, 2000 to today) from BFS table T3.3.0.1. Explicitly differentiates from siblings by naming what it does NOT provide — monthly values and cantonal breakdowns — and flags the SECO-vs-ILO distinction, so an agent can separate it from seco_get_monthly_report_url and seco_get_youth_unemployment without opening schemas.

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 clear when-to-use context (annual national series) and explicit exclusions (monthly, cantonal — both get a refusal). Points to amstat.ch as the interactive fallback. It stops short of naming sibling tools like seco_get_monthly_report_url as direct alternatives, but the exclusion guidance is concrete and actionable.

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

Deploy Server