Skip to main content
Glama

Belgium Data Desk

Get one dataset record

get_dataset
Read-only

Full catalogue record for one dataset id from search_datasets: publisher, licence and what it allows, update cycle, contact, description, file links, publisher-declared columns, link-check evidence, and whether preview_dataset can read the file. For files checked weekly it adds a dataset card computed from the file itself: whether it is overdue against its declared update cycle, the period the data covers, join keys (NIS municipality codes incl. pre-2025 codes, enterprise numbers, postcodes, coordinates), sparse and constant columns, column changes since the last check, and quotable facts each with its evidence. Fields the publisher leaves empty are listed under not_declared_by_publisher with the source page; for analysis over the whole file, the analysis block gives download links and the domains a sandbox must allow. Example: {"id":"national:d04b704a-1672-4567-bf0d-9a9452618812"}.

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": {
      "id": "<id>"
    },
    "name": "get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDataset id as returned by search_datasets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the description is free to add behavior it alone can supply — the conditional dataset card for weekly-checked files, the not_declared_by_publisher bucket with source page, and the analysis block listing download links and sandbox-permitted domains. These are exactly the traits an agent needs before committing to a call and could not infer from structured fields.

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?

Purpose is front-loaded in the first clause, before the field enumeration and the conditional/edge-case behavior. It is a dense single paragraph and the enumerated field list is long, but every item carries information an agent would otherwise have to discover by calling; no filler sentences.

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

Completeness5/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 must carry the return-shape burden — and it does, covering the base catalogue fields, the conditional computed dataset card, the not_declared_by_publisher handling, and the analysis block. For a read-only single-record lookup of this complexity, nothing an agent needs to call it correctly is missing.

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% and the single id param is already documented, so the baseline would be 3. The description earns an extra point by showing a concrete id example ('national:d04b704a-...'), which conveys the namespaced format that the schema description does not.

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 ('Full catalogue record for one dataset id') and immediately ties the id source to the sibling search_datasets. Enumerating the record's contents (publisher, licence, update cycle, contact, file links, join keys) makes it unmistakable versus preview_dataset or the domain-specific tools.

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?

The 'from search_datasets' phrasing plus the preview_dataset cross-reference ('whether preview_dataset can read the file') implicitly routes the agent: search first, use this for the full record, preview for reading the file. It also flags the alternative path for whole-file work via the analysis block. No explicit when-not-to-use statement, so it falls short of a 5.

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.