Skip to main content
Glama

Browse the BFS STAT-TAB table tree

browse_bfs_tables
Read-only

Browse the BFS PXWeb database tree: list all STAT-TAB tables, drill into a path for child nodes, and filter titles by substring to find relevant Swiss statistics.

Instructions

List entries of the BFS PXWeb database tree. Without 'path' lists all STAT-TAB databases (at BFS each is one table, id like 'px-x-1003020000_101', with its title); with 'path' lists that node's children (type level/table, text, updated). Use 'filter' to substring-match titles. Examples: {filter:'Wohnbevölkerung', lang:'de'}, {path:'px-x-0102010000_101'}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_bfs_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of titles/labels: de, fr, it or en (default en)en
pathNoNode path, e.g. 'px-x-0102010000_101'. Omit for the root listing.
limitNo
filterNoCase/diacritic-insensitive substring filter on titles or ids
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish read-only and open-world behavior, and the description adds useful return-shape details: root results include table ids and titles, while child results include type, text, and update information. It does not mention pagination behavior, but otherwise adds meaningful context beyond annotations.

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 front-loaded and compact, moving directly from root/child behavior to filtering and examples. Every sentence provides operational value without unnecessary wording.

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?

For a tree-browsing tool without an output schema, the description explains the main return fields and usage modes well enough to call it correctly. The remaining gap is pagination behavior for 'limit' and 'offset'.

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 60%, and the description adds concrete examples for 'path', 'filter', and 'lang'. It does not compensate for the undocumented 'limit' and 'offset' parameters or explain pagination.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: listing entries of the BFS PXWeb database tree. It clearly explains the root-listing vs child-listing behavior, but it does not explicitly distinguish the tool from the sibling search_bfs_tables.

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?

It gives conditional usage for 'path' (omit for root listing, provide to list children) and mentions 'filter' for substring matching. However, it does not say when to use this browser versus search_bfs_tables or get_bfs_table_metadata.

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