Skip to main content
Glama

nbb_compare

Read-onlyIdempotent

Align 2–5 SDMX series on a common time index and downsample finer frequencies to the coarsest using closing aggregation for comparable economic indicator analysis.

Instructions

Align 2-5 SDMX series on a common time index. Each series is specified as {dataflow_id, agency?, key? | filters?, label?} and must resolve to a single series. Downsamples finer frequencies to the coarsest using closing (last-of-period) aggregation.

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": {
      "series": "<series>"
    },
    "name": "nbb_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesYes
frequencyNo
end_periodNo
max_periodsNo
start_periodNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), so the bar is lower, and the description adds genuinely useful behavior: finer frequencies are downsampled to the coarsest using closing (last-of-period) aggregation. It also signals a failure mode via the single-series resolution requirement, though it does not say what error or output shape results when resolution fails.

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?

Three sentences, front-loaded with the core action, then the input shape, then the aggregation rule. Dense but every sentence carries information; the brace-notation for the series object is compact rather than bloated.

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 exists, so return values need no explanation, and the aggregation semantics are a genuine plus. But for a 5-parameter tool with zero schema description coverage and no sibling routing guidance, the missing frequency/period-window semantics leave an agent guessing how to bound the comparison window.

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 compensate, and it only partially does: it documents the per-series object fields ({dataflow_id, agency?, key? | filters?, label?}) but says nothing about frequency, start_period, end_period, or max_periods (including the 200 default). Meaning is added for one parameter out of five, leaving the period-window controls undocumented anywhere.

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 ('Align 2-5 SDMX series on a common time index') with an explicit arity limit. The alignment/comparison framing is clearly distinct from retrieval-oriented siblings like nbb_query or nbb_search, so an agent can route on it 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real prerequisite - each series 'must resolve to a single series' - and bounds the input at 2-5, which tells the agent when input is valid. However, it never states when to prefer this over nbb_query or nbb_quick for the same identifiers, and offers no exclusions, so usage is only implied.

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