Schwaizer BFS MCP Server

get_sse_metadata

Retrieve metadata for a Swiss Stats Explorer dataset, including available dimensions and their values, to identify applicable filters before querying data.

Instructions

Get metadata for a Swiss Stats Explorer (SSE) dataset. Returns available dimensions and their possible values. Use this before calling get_sse_data to understand what filters you can apply.

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": {
      "numberBfs": "<numberBfs>"
    },
    "name": "get_sse_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`numberBfs`	Yes	BFS dataset identifier for SSE (e.g., "DF_LWZ_1")
`language`	No	Language for dimension and value labels	en

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It transparently describes it as a read-only metadata retrieval operation returning dimensions and values. No destructive effects or additional behaviors are implied, which is appropriate for this function.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with no wasted words. The action verb 'Get' is front-loaded, and the important usage guidance is included efficiently.

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?

Given two parameters, no output schema, and multiple sibling tools, the description sufficiently explains the output (dimensions and values) and the tool's role. It could elaborate on language parameter effects but overall complete.

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 coverage is 100% with descriptions already defining numberBfs and language. The description adds workflow context but no new semantic detail beyond the schema. Baseline of 3 is appropriate.

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?

The description clearly states it 'Gets metadata for a Swiss Stats Explorer (SSE) dataset' and specifies it 'Returns available dimensions and their possible values.' It differentiates itself from siblings like get_sse_data by framing itself as a prerequisite step.

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 explicitly advises 'Use this before calling get_sse_data to understand what filters you can apply,' providing clear context and sequence. However, it does not mention when not to use it or alternatives like get_dataset_dimensions.

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

Deploy Server