Skip to main content
Glama
bcb-mcp
by msperlin

Search Series

search_series
Read-only

Finds Brazilian Central Bank SGS series IDs from natural-language queries, with optional category filters and live catalog search, so you can retrieve the correct time-series data.

Instructions

Find BCB-SGS series ids from natural language.

Searches the bundled curated dictionary (151 key Brazilian macro series, with Portuguese and English aliases) and, optionally, the official BCB catalog. Always call this before get_series() when you do not know the id.

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": {
      "query": "<query>"
    },
    "name": "search_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFree-text search, e.g. 'unemployment', 'selic', 'desemprego', 'consumer prices', 'public debt', 'credito'.
categoryNoOptional dictionary category filter, e.g. 'inflation', 'labor', 'external_sector', 'fiscal', 'credit', 'activity'.
max_resultsNoMaximum number of matches to return (1..500).
include_onlineNoAlso query the live BCB-SGS catalog (English names). Set to false for an offline, dictionary-only search.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 description's added value is disclosing the two data sources, the dictionary size and bilingual aliases, and the offline mode via include_online=false. It omits behavior on zero matches and any caveats about the live catalog query (latency/failure handling).

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 short sentences, front-loaded with the purpose, then the sources, then the imperative usage rule. No filler or repetition.

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 and annotations covering safety, the description supplies what is needed: purpose, data sources, and the sequencing rule with get_series. Only minor gaps remain, such as what an empty result means or how online results differ from dictionary hits.

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 100% and the schema already describes query, category, max_results and include_online in detail, so the description adds little parameter meaning beyond reinforcing the dictionary's bilingual aliasing. Baseline 3 applies when the schema does the heavy lifting.

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 concrete verb+resource ('Find BCB-SGS series ids from natural language') and names the underlying sources (bundled curated dictionary of 151 series, optional official BCB catalog). It also distinguishes itself from get_series by positioning itself as the id-lookup step that precedes it.

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?

Explicitly says to call this before get_series() when the id is unknown, which is a clear when-to-use rule. It does not address when to prefer browsing siblings like list_series or list_categories instead of a free-text search.

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