Skip to main content
Glama

Search BFS STAT-TAB statistical tables

search_bfs_tables
Read-only

Search Federal Statistical Office (BFS) STAT-TAB tables by keywords to get table IDs and titles for metadata retrieval and data queries.

Instructions

Find Federal Statistical Office (BFS) tables on STAT-TAB by keywords: population, births, deaths, migration, tourism overnight stays, crime, students, vehicles, buildings, enterprises and hundreds more. Returns table ids (e.g. 'px-x-0102010000_101') with titles, to pass to get_bfs_table_metadata then query_bfs_table. Titles are in the chosen language, so use matching search terms (e.g. lang='de', query 'Logiernächte Kanton'). Examples: {query:'population commune age'}, {query:'hotel overnight stays', lang:'en'}.

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": {
      "query": "<query>"
    },
    "name": "search_bfs_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of titles/labels: de, fr, it or en (default en)en
limitNo
queryYesKeywords, e.g. 'population canton', 'Straftaten', 'overnight stays'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavior: the return payload is table ids with titles (e.g. 'px-x-0102010000_101') and titles follow the requested language — relevant since there is no output schema.

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 purpose, then return value, then chaining, then examples — a sensible order with no filler. It is a single dense block, but every sentence carries information an agent would need.

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 no output schema and only three parameters, the description covers what is searched, what comes back, and what to call next, which is enough to invoke it correctly. The only gap is limit behavior (default 15, max 50) and result ordering, which are left to the schema.

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 67% and the description adds meaning beyond it by tying lang to the language of returned titles and therefore to the wording of the query itself, with a worked example ('lang="de", query "Logiernächte Kanton"'). The limit parameter remains unexplained in both places.

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 a specific verb and resource ('Find BFS tables on STAT-TAB by keywords') and enumerates the statistical domains covered, which separates it from the generic search_datasets/search_data_cubes siblings. It also names the downstream pipeline (get_bfs_table_metadata then query_bfs_table), so the agent knows exactly what the tool produces.

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 strong positive guidance: keyword style, matching the search language to the lang parameter, and concrete example calls. It doesn't state when to prefer browse_bfs_tables over keyword search, so the closest alternative is left implicit.

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

Deploy Server

Other Tools