Skip to main content
Glama
bcb-mcp
by msperlin

Get Series Stats

get_series_stats
Read-only

Summarizes Brazilian Central Bank SGS series with last value, min, max, mean, and change, so you can answer with key numbers without retrieving full observation history.

Instructions

Compact summary of each series (last value, min, max, mean, change) without the raw rows.

Use this when you need the numbers for a narrative answer and do not need the full observation history.

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_ids": "<series_ids>"
    },
    "name": "get_series_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
last_dateNoEnd date (YYYY-MM-DD). Defaults to today.
use_cacheNoReuse cached parquet data (default) or force a refresh.
first_dateNoStart date (YYYY-MM-DD). Defaults to five years before last_date.
series_idsYesSGS series identifiers. Each item may be a numeric SGS id (11) or a dictionary alias in English/Portuguese ('selic', 'ipca', 'desemprego', 'dolar'). Use search_series() when unsure.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that, the description usefully discloses the aggregation shape returned (last value, min, max, mean, change) and that raw rows are excluded, which tells the agent about output size and content. It does not mention that data is fetched from an upstream source with possible latency or that caching affects freshness, both of which matter for a network-backed read.

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?

Two sentences, front-loaded with what is returned, followed by the decision rule for using it. No filler, repetition, or restated title.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain return structure, and it still summarizes it helpfully; annotations cover safety and the 100%-covered schema covers all four parameters. The one remaining gap is not naming the sibling raw-data tool as the explicit alternative when full history is needed.

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 100%, including aliases, date defaults, and the cache flag, so the schema does the heavy lifting. The description adds only 'each series', implying batch input, and no detail on date-range or cache semantics beyond what the schema states — the baseline 3 for full coverage applies.

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?

The description names a concrete resource (each series) and enumerates the exact outputs (last value, min, max, mean, change), so the agent knows precisely what it produces. It also implicitly separates itself from raw-row retrieval via 'without the raw rows', though it never names the sibling (e.g., get_series) that would make the distinction unambiguous.

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 gives an explicit trigger — 'when you need the numbers for a narrative answer' — and an explicit exclusion — 'do not need the full observation history'. This is strong conditional guidance, but it stops short of pointing at the concrete alternative tool to call instead.

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