Schwaizer BFS MCP Server

get_dataset_dimensions

Retrieve dimensions and possible values for a PXWEB dataset to understand which filters can be applied when querying data.

Instructions

Get a simplified view of available dimensions and their values for a PXWEB dataset. This is useful for quickly understanding what filters you can apply when querying data. Returns dimension codes and all possible values.

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_dataset_dimensions"
  }
}

Input Schema

Name	Required	Description	Default
`numberBfs`	Yes	BFS number (FSO number) of the dataset
`language`	No	Language for dimension labels	en

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavior. It describes the return (dimension codes and values) but does not explicitly state read-only nature or limitations.

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?

Three sentences, each adding value: defines the action, states usefulness, and describes return. No redundancy.

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 simple parameters and no output schema, the description adequately covers purpose and return, but could be improved by specifying output format or structure.

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 description adds no new meaning beyond the schema's parameter descriptions; it only restates the same information.

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 the verb ('Get') and resource ('simplified view of available dimensions and their values for a PXWEB dataset'), and distinguishes itself from siblings by focusing on dimensions for filtering, not metadata or data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for understanding filters before querying ('useful for quickly understanding what filters you can apply'), but does not explicitly state when not to use or provide alternatives among siblings.

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

Deploy Server