Skip to main content
Glama
Sign In

apibase

by io.github.whiteknightonhorse
OverviewDiscussionsAdmin

Statbel Datasource Detail

statbel.catalog.datasource_detail
Read-onlyIdempotent

Get full metadata (multilingual descriptions, supported locales, category, last data and metadata update timestamps) for one Statbel datasource, identified by the datasource_id from statbel.list_datasources. An invalid or unpublished id returns an empty upstream response. Data: bestat.statbel.fgov.be, Belgian statistics office, no auth required.

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": {
      "datasource_id": "<datasource_id>"
    },
    "name": "statbel.catalog.datasource_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasource_idYesDatasource UUID from statbel.list_datasources (e.g. "e957ac31-44a2-4718-8469-10470d3c41d9"). An invalid or unpublished id returns an empty upstream response.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds the key behavioral fact that invalid or unpublished ids return an empty upstream response, plus the no-auth requirement and the data source, which are useful beyond the 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?

Three dense sentences: the purpose, the edge case, and the access context. Every sentence carries information, and the main verb and object are front-loaded with no filler.

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?

For a single-parameter read-only tool with a rich schema, an output schema, and clear annotations, the description covers all needed essentials: what it returns, where the id comes from, invalid-id behavior, data source, and authentication. Nothing an agent needs is missing.

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?

The schema itself already documents the datasource_id parameter with the same reference to statbel.list_datasources, an example UUID, and the empty-response behavior. With 100% schema coverage, the description adds no additional parameter meaning; baseline 3 is appropriate.

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?

The description uses a specific verb ('Get full metadata') and resource ('one Statbel datasource'), listing the exact fields (multilingual descriptions, supported locales, category, timestamps). It inherently distinguishes this detail endpoint from sibling list and data-query 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?

It tells the agent to obtain the datasource_id from statbel.list_datasources, and notes the empty-response case for invalid ids. While it doesn't explicitly contrast with statbel.catalog.view_data, the reference to the list tool and the focus on metadata imply the appropriate use case.

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

All apibase toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources