Skip to main content
Glama

nbb_query

Read-onlyIdempotent

Fetch SDMX statistical data from the National Bank of Belgium using a dataflow ID, raw keys or field filters, and optional period or observation limits for context-controlled results.

Instructions

Generic SDMX data fetch. Specify either 'key' (raw SDMX, e.g. 'D.USD') or 'filters' ({'FREQ':'D','EXR_CURRENCY':'USD'}; a list value means OR). Supports start_period, end_period, last/first_n_observations (per series). max_observations caps returned rows and max_series caps per-series stats to keep the response within the model's context budget.

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": {
      "dataflow_id": "<dataflow_id>"
    },
    "name": "nbb_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
agencyNoBE2
formatNosummary
filtersNo
versionNo
end_periodNo
max_seriesNo
dataflow_idYes
start_periodNo
max_observationsNo
last_n_observationsNo
first_n_observationsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, so the safety profile is covered. The description adds behavior beyond that: last/first_n apply per series, and max_observations/max_series exist to keep responses within the context budget, which signals truncation is possible. It stops short of saying whether truncation is flagged in the response, so not a 5.

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?

Dense but well ordered: purpose first, then the key/filters selector, then temporal and row-limiting options. Parenthetical examples earn their space. A couple of clauses are compressed to the point of terseness ('max_series caps per-series stats'), but there is no filler.

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 12 parameters, a required argument, and no schema descriptions, the description carries heavy burden. An output schema exists so return values need no explanation, but the required dataflow_id and the format switch (which likely changes response shape) are missing, leaving gaps an agent would need to trial-and-error.

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 0% across 12 parameters, so the description must compensate, and it does explain the semantics of key, filters (including OR for lists), start_period, end_period, last/first_n_observations, max_observations, and max_series. However, the required dataflow_id is never described, and agency, version, and especially format (default 'summary') are left entirely undefined.

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?

Opens with a specific verb+resource ('SDMX data fetch') and names the selector mechanism (key or filters). It does not differentiate itself from siblings like nbb_quick or nbb_compare, so an agent still has to guess which query entry point to pick, but the core operation is unambiguous.

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?

Provides real intra-tool guidance: 'Specify either key or filters', plus the OR semantics for list filter values. It gives no when-to-use context relative to nbb_quick/nbb_compare/nbb_describe, so the agent gets parameter routing but not tool routing.

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