Skip to main content
Glama
Sign In
mcp-server-brasil

mcp-server-brasil

by vicgamelo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Indicador econômico (BCB)

indicador_economico
Read-onlyIdempotent

Fetches recent values for Brazilian Central Bank indicators—Selic, CDI, IPCA, IGP-M, dollar, and euro—to support economic and financial analysis.

Instructions

Últimos valores de um indicador do Banco Central (SGS): selic_meta, selic, cdi, ipca, igpm, dolar ou euro.

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": {
      "indicador": "<indicador>"
    },
    "name": "indicador_economico"
  }
}

Input Schema

NameRequiredDescriptionDefault
ultimosNo
indicadorYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the key traits (readOnlyHint, idempotentHint, openWorldHint), and the description adds that data comes from Banco Central SGS, which is useful provenance. It does not disclose update frequency or granularity (e.g., whether 'selic' is daily and 'ipca' monthly), which matters for interpreting 'últimos valores'.

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 front-loaded sentence that names the source and the valid indicators with no filler. The enum enumeration duplicates the schema slightly, but it is short enough not to be a real cost.

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?

With an output schema present, return values need not be described, and the indicator set is fully covered. The gap is the unexplained 'ultimos' window and the differing periodicity of daily versus monthly indicators, which an agent needs in order to call the tool correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 the parameter burden, and it only restates the enum values already declared in the schema. The 'ultimos' parameter (default 12, presumably the number of most recent observations) is never explained in either place, leaving its unit and meaning ambiguous.

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 gives a specific verb-and-resource pair ("Últimos valores de um indicador do Banco Central (SGS)") and enumerates the seven accepted indicators, so an agent immediately knows it retrieves recent time-series values from BCB SGS. It does not mention any sibling, but none of the sibling tools (CEP, CNPJ, DDD, holidays, municipalities, document validation) overlap with economic indicators, so confusion is unlikely.

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?

Usage is only implied by the indicator list; there is no explicit statement of when to pick this tool, no note that it is a live external lookup (openWorldHint), and no guidance such as "use for current market rates, not historical series." An agent can infer the use case from the name and enum, but nothing in the text steers it.

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

Deploy Server

Other Tools