Skip to main content
Glama

nbb_quick

Read-onlyIdempotent

Retrieve headline National Bank of Belgium indicators by topic, such as exchange rates, inflation, GDP, or unemployment, with frequency and currency filters, routing queries to the correct series.

Instructions

Topic-based shortcut for common queries (exchange_rate, inflation_hicp, gdp, unemployment_rate, government_debt, policy_rate, mortgage_rate, consumer_confidence, trade_balance, …). Routes to the right dataflow and headline series. 'frequency' (A/S/Q/M/D) applies to every topic; 'currency' only to exchange_rate, e.g. nbb_quick('exchange_rate', currency='USD').

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": {
      "topic": "<topic>"
    },
    "name": "nbb_quick"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes
formatNosummary
currencyNo
frequencyNo
end_periodNo
max_seriesNo
start_periodNo
max_observationsNo
last_n_observationsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations by explaining automatic routing and the topic-specific applicability of frequency and currency, though it does not discuss limits, pagination, or result sizing.

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?

The description is compact and front-loaded: it states the tool's role first, then the topic examples, then the scoping rules for frequency and currency. The example call is directly useful and every sentence earns its place.

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?

An output schema and safety annotations reduce the burden, and the description explains the central topic-routing behavior. However, for a 9-parameter tool with 0% schema description coverage, it leaves several behaviorally important parameters unexplained, so it is only minimally complete.

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 description coverage is 0%, so the description must carry parameter meaning. It adds valuable semantics for topic, frequency, and currency, but leaves format, start_period, end_period, max_series, max_observations, and last_n_observations undocumented, which is a significant gap across 9 parameters.

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 gives a specific verb-and-resource framing: a topic-based shortcut that routes common economic topics to the right dataflow and headline series. It lists concrete topics such as exchange_rate, inflation_hicp, gdp, and unemployment_rate, so an agent can identify its purpose without opening the schema.

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 clearly frames the tool as a shortcut for common queries and explains that frequency applies to every topic while currency applies only to exchange_rate, with an example. It does not explicitly say when to avoid it in favor of nbb_query or nbb_compare, so the guidance is clear but incomplete.

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