Skip to main content
Glama
malkreide

swiss-statistics-mcp

by malkreide

bfs_education_stats

Read-onlyIdempotent

Retrieve Swiss education statistics on teachers, students, enrollment scenarios, and scholarships. Filter by canton to get targeted data without needing table IDs.

Instructions

Retrieve Swiss education statistics — convenience tool for Schulamt context.

Provides direct access to key education datasets without needing to know table IDs or variable codes. Covers teachers, students, enrollment scenarios, and scholarship data, optionally filtered by canton.

Args: params (GetEducationStatsInput): - topic (str): One of: 'teachers', 'students', 'scenarios', 'scholarships' - canton (Optional[str]): Canton name, e.g. 'Zürich'. None = all cantons. - lang (str): Language code

Returns: DataTableResult with topic, topic_description, canton_filter on success, plus the data table fields. On error, error and hint are set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
hintNo
table_idNo
titleNo
sourceNo
updatedNo
languageNo
dimensionsNo
rows_totalNo
rows_returnedNo
truncatedNo
rowsNo
noteNo
cantons_comparedNo
canton_variableNo
topicNo
topic_descriptionNo
cantonNo
canton_filterNo
regionNo
breakdownNo
yearNo
Behavior4/5

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

The description aligns with annotations (readOnlyHint=true, etc.) and adds detail on return format (DataTableResult with topic, canton_filter, error/hint fields). No contradictions, and it elaborates on parameter effects.

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?

The description is concise and well-structured with Args/Returns sections, front-loaded purpose, and no unnecessary words.

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?

Given the rich input schema, annotations, and presence of an output schema, the description covers all essential aspects: purpose, parameters, return shape, and error handling.

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 descriptions already cover all three parameters. The description restates them but adds little new beyond the schema. High schema coverage sets baseline at 3.

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 explicitly states it retrieves Swiss education statistics as a convenience tool for the Schulamt context, listing specific topics (teachers, students, scenarios, scholarships) and filtering by canton. It differentiates from siblings like bfs_get_data by noting no need for table IDs.

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 clearly indicates this is for common education topics without table IDs, implying use over bfs_get_data. However, it does not explicitly state when not to use it or provide alternative tool names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malkreide/swiss-statistics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server