Skip to main content
Glama

SourceGeek

Get CBS table structure

cbs_table_info
Read-only

Describe a CBS (Statistics Netherlands) StatLine table: title, summary, period, status, its topics (measured values with unit and decimals) and its dimensions (e.g. region, period, sector, occupation) with their category keys and labels. Periods are listed newest last and marked final or provisional.

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": {
      "tableId": "<tableId>"
    },
    "name": "cbs_table_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableIdYesCBS StatLine table identifier, e.g. '83599NED'.
dimensionNoDimension key that categorySearch applies to, e.g. 'RegioS'. Omit to search every dimension.
categoryLimitNoMaximum categories listed per dimension (1-500, default 50); periods list the most recent ones. Each dimension also reports its full categoryCount.
categorySearchNoOnly list categories whose label or key contains this text, e.g. 'Utrecht', 'ICT', '2025'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered; the description adds genuine behavioral detail beyond that, notably that periods are ordered newest-last and flagged final or provisional. It does not cover auth/rate-limit behavior or what happens with an unknown tableId, but the added return-shape semantics are substantive.

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?

A single dense sentence, front-loaded with the verb and resource, with the field inventory and ordering behavior following. The parentheticals are information-bearing rather than filler, though the sentence is long enough that the period-ordering rule risks being skimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing returns, and it does list the main fields well. However, for a 4-parameter tool with truncation behavior (categoryLimit default 50) and filtering, the description says nothing about how results are limited or filtered, leaving the agent to rely entirely on the schema for call correctness.

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%, so tableId, dimension, categoryLimit, and categorySearch are fully documented in the schema itself, making 3 the baseline. The description adds only indirect context - that dimensions come with category keys and labels - and does not explain the interplay of dimension/categorySearch/categoryLimit, so it adds little beyond the schema.

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?

Names a specific verb ('Describe') and resource ('CBS StatLine table') and then enumerates exactly what is returned: title, summary, period, status, topics with unit/decimals, and dimensions with category keys and labels. This clearly separates it from cbs_query_data (data retrieval) and cbs_search_tables (discovery), though it never names or explicitly contrasts those siblings.

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 metadata-oriented content implies the use case (inspecting a table's structure before querying it), but there is no explicit statement of when to use this versus cbs_query_data or cbs_search_tables, and no prerequisites or exclusions are given. The agent must infer the workflow position from the returned-field list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources