Skip to main content
Glama

SourceGeek

Get CBS statistics

cbs_query_data
Read-only

Fetch observations from a CBS (Statistics Netherlands) StatLine table, filtered by dimension category keys. Rows carry the category label for each dimension and the value of each requested topic; the response lists the topics' units and says whether rows were cut off at the limit.

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_query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return (1-1000, default 200).
topicsNoTopic keys from the table description to return, e.g. ['M001298']. Omit for every topic in the table.
filtersNoCategory filters per dimension. Dimensions without a filter return every category.
tableIdYesCBS StatLine table identifier, e.g. '83599NED'.
latestPeriodsNoKeep only the N most recent periods. Ignored when filters already select periods.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful return-shape context (per-dimension category labels, topic values, unit listing, truncation indicator), but says nothing about rate limits, error behavior, or what a truncated result implies for follow-up calls.

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 dense sentences, front-loaded with the verb and resource, then the response contract. No filler, though the second sentence packs several distinct facts (row labels, topic values, units, truncation) into one clause chain.

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?

With no output schema, the description usefully sketches the response (labels, values, units, truncation flag), which is the main gap it must fill. It still omits how a truncated result should be handled (there is no offset parameter) and gives no guidance on resolving tableId or topic keys beyond a bare reference to 'the table description'.

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 coverage is 100%, so all five parameters are already well documented, including filter defaults and the latestPeriods precedence rule. The description reinforces that topics map to values in returned rows and that filters operate on category keys, but adds no naming, format, or interaction detail 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?

States a specific verb and resource ('Fetch observations from a CBS StatLine table') plus the filtering basis (dimension category keys), which is clearly distinct from table search or table-metadata siblings. It never names those siblings explicitly, so the agent must infer the lookup-then-fetch workflow.

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 only implied: topic keys are said to come 'from the table description', hinting that a metadata call precedes this one, and the latestPeriods note gives a conditional rule. There is no explicit when-to-use-this-instead guidance or statement of prerequisites such as where tableId comes from.

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