Skip to main content
Glama
bcb-mcp
by msperlin

List Series

list_series
Read-only

Browse a curated dictionary of Brazilian Central Bank SGS time series, optionally filtered by category, to identify series for later data retrieval.

Instructions

Browse the curated dictionary, optionally restricted to one category.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of series to list (1..500).
categoryNoOptional category key, e.g. 'inflation'. Omit to list everything.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds the useful detail that the catalog is "curated" (a fixed, bounded set), which is consistent with the closed-world hint, but it says nothing about the default page size of 200, the 500 cap, or what happens when the limit truncates results.

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?

A single tight sentence with no filler, and the core action is front-loaded. It is arguably too terse rather than padded, but nothing in it is wasted.

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 both parameters are fully documented in the schema. What is missing is the navigational context an agent needs to pick this tool over its five closely related siblings in a list/search/get family.

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%, and the schema already explains limit ranges and the optional category key with an example. The description's "optionally restricted to one category" merely paraphrases the category parameter and adds no format or behavior detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Browse the curated dictionary" gives a verb and a resource, but the resource is called a "dictionary" rather than a series list, so the agent must lean on the tool name and title to know what is actually being listed. It also makes no attempt to distinguish itself from siblings such as search_series or get_series, leaving the browse-vs-search boundary implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The only usage signal is "optionally restricted to one category," which describes a filter rather than when to choose this tool. There is no statement about when to prefer search_series, get_series, or list_categories, and no exclusion guidance.

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