Skip to main content
Glama

SourceGeek

Search CBS statistics tables

cbs_search_tables
Read-only

Search the CBS (Statistics Netherlands) StatLine open-data catalog for statistical tables by keyword. Every word must appear in a table's title or description. Returns matching tables with their id, title, summary, status (regular or discontinued), last modification, number of values and a StatLine link; the table's own description adds the period covered and update frequency.

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": "cbs_search_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of tables to return (1-50, default 10).
queryYesDutch keywords to find in table titles and descriptions, e.g. 'vacatures beroep', 'werkloosheid provincie', 'cao lonen'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), yet the description still adds real information: the AND-matching rule across title/description, the fact that results include a status of regular or discontinued, and that the table's own description carries period covered and update frequency. It does not cover no-match behavior or result ordering.

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?

Two sentences, front-loaded with the action and resource, with the return-field enumeration serving a real purpose because there is no output schema. The second sentence is long and semicolon-joined but every clause conveys distinct result information.

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, the description compensates by listing the returned fields and the extra metadata in the table description. Combined with annotations covering safety and full schema coverage on both parameters, an agent has enough to call it correctly; only no-result and ordering behavior remain unspecified.

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 100%, so the baseline is 3, but the description adds meaning the schema lacks by explaining that every query word must appear in the title or description — this defines the matching semantics an agent needs to construct good queries. It adds nothing about limit beyond the schema, which is acceptable given full coverage.

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?

States a specific verb and resource: 'Search the CBS (Statistics Netherlands) StatLine open-data catalog for statistical tables by keyword.' It also enumerates the returned fields, so an agent knows exactly what it gets. It stops short of naming the sibling tools (cbs_query_data, cbs_table_info) that an agent would otherwise confuse it with.

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?

Usage is implied by the matching rule ('Every word must appear in a table's title or description'), which tells the agent how to phrase a query but not when to pick this tool over cbs_query_data or cbs_table_info. There are no explicit when-not conditions or alternative routing.

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