Skip to main content
Glama
Sign In

FalaZuki Finance BR

by com.falazuki
OverviewDiscussionsAdmin

get_rates_history

Retorna série histórica de uma taxa econômica brasileira (Selic, CDI, IPCA, IGP-M, dólar, euro, salário mínimo). Dados oficiais do Banco Central — séries SGS. Permite filtrar por intervalo de datas e agregar em mensal/anual pra reduzir volume.

Input Schema

NameRequiredDescriptionDefault
toNoData final em YYYY-MM-DD (opcional)
fromNoData inicial em YYYY-MM-DD (opcional)
limitNoLimite de pontos retornados (default 500, max 2000)
metricYesMétrica desejada. selic/cdi/dollar/euro são diárias; o resto é mensal. ipca e igpm vêm acumulados em 12 meses; selicMonthly, ipcaMonthly, igpmMonthly, inpcMonthly, ipca15Monthly, ipcaeMonthly, igpdiMonthly, inccMonthly, inccmMonthly, ipcFipeMonthly, tr e poupanca são a variação do mês. A série da poupança começa em 06/2012, com a regra da Lei 12.703/2012.
aggregateNoAgregação: 'none' retorna pontos brutos, 'monthly' retorna 1 ponto/mês (último valor), 'yearly' retorna 1 ponto/ano.none

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / metric / description
      Previous value: -"Métrica desejada. selic/cdi/dollar/euro são diárias; o resto é mensal. ipca e igpm vêm acumulados em 12 meses; selicMonthly, ipcaMonthly, igpmMonthly, inpcMonthly, tr e poupanca são a variação do mês. A série da poupança começa em 06/2012, com a regra da Lei 12.703/2012."New value: +"Métrica desejada. selic/cdi/dollar/euro são diárias; o resto é mensal. ipca e igpm vêm acumulados em 12 meses; selicMonthly, ipcaMonthly, igpmMonthly, inpcMonthly, ipca15Monthly, ipcaeMonthly, igpdiMonthly, inccMonthly, inccmMonthly, ipcFipeMonthly, tr e poupanca são a variação do mês. A série da poupança começa em 06/2012, com a regra da Lei 12.703/2012."
    • changedInput schema / properties / metric / enum
      Previous value: -[
-  "selic",
-  "selicMonthly",
-  "cdi",
-  "ipca",
-  "ipcaMonthly",
-  "igpm",
-  "igpmMonthly",
-  "inpcMonthly",
-  "jurosChequeEspecial",
-  "jurosRotativo",
-  "jurosPessoalNaoConsignado",
-  "jurosConsignadoInss",
-  "jurosVeiculos",
-  "jurosCreditoPfTotal",
-  "dollar",
-  "euro",
-  "minimumWage",
-  "tr",
-  "poupanca"
-]New value: +[
+  "selic",
+  "selicMonthly",
+  "cdi",
+  "ipca",
+  "ipcaMonthly",
+  "igpm",
+  "igpmMonthly",
+  "inpcMonthly",
+  "ipca15Monthly",
+  "ipcaeMonthly",
+  "igpdiMonthly",
+  "inccMonthly",
+  "inccmMonthly",
+  "ipcFipeMonthly",
+  "jurosChequeEspecial",
+  "jurosRotativo",
+  "jurosPessoalNaoConsignado",
+  "jurosConsignadoInss",
+  "jurosVeiculos",
+  "jurosCreditoPfTotal",
+  "dollar",
+  "euro",
+  "minimumWage",
+  "tr",
+  "poupanca"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / metric / description
      Previous value: -"Métrica desejada. selic/cdi/dollar/euro são diárias; o resto é mensal. ipca e igpm vêm acumulados em 12 meses; ipcaMonthly, igpmMonthly, inpcMonthly, tr e poupanca são a variação do mês. A série da poupança começa em 06/2012, com a regra da Lei 12.703/2012."New value: +"Métrica desejada. selic/cdi/dollar/euro são diárias; o resto é mensal. ipca e igpm vêm acumulados em 12 meses; selicMonthly, ipcaMonthly, igpmMonthly, inpcMonthly, tr e poupanca são a variação do mês. A série da poupança começa em 06/2012, com a regra da Lei 12.703/2012."
    • changedInput schema / properties / metric / enum
      Previous value: -[
-  "selic",
-  "cdi",
-  "ipca",
-  "ipcaMonthly",
-  "igpm",
-  "igpmMonthly",
-  "inpcMonthly",
-  "jurosChequeEspecial",
-  "jurosRotativo",
-  "jurosPessoalNaoConsignado",
-  "jurosConsignadoInss",
-  "jurosVeiculos",
-  "jurosCreditoPfTotal",
-  "dollar",
-  "euro",
-  "minimumWage",
-  "tr",
-  "poupanca"
-]New value: +[
+  "selic",
+  "selicMonthly",
+  "cdi",
+  "ipca",
+  "ipcaMonthly",
+  "igpm",
+  "igpmMonthly",
+  "inpcMonthly",
+  "jurosChequeEspecial",
+  "jurosRotativo",
+  "jurosPessoalNaoConsignado",
+  "jurosConsignadoInss",
+  "jurosVeiculos",
+  "jurosCreditoPfTotal",
+  "dollar",
+  "euro",
+  "minimumWage",
+  "tr",
+  "poupanca"
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the data source (Banco Central SGS), that official data is returned, and that series have varying granularity — useful context. However, it does not mention rate limits, error behavior when dates are out of range, or return structure beyond the series concept.

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 compact sentences that front-load the purpose, then the data source and filtering/aggregation capability. No filler sentences.

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?

For a read-only history fetch with 100% schema coverage of 5 params and no output schema, the description gives enough orientation (what, source, filtering). Missing only explicit return-format expectations and behavior on invalid ranges, which keeps it just short of 5.

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%, so the detailed metric semantics (daily vs monthly, accumulated vs monthly variation, savings series starting 06/2012) already live in the schema. The description adds only the high-level notion of date filtering and aggregation, which is already documented in the schema. Baseline 3 applies.

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?

Specific verb+resource: returns the historical series of a Brazilian economic rate (Selic, CDI, IPCA, etc.), naming the data source (SGS/BCB). Clearly distinct from sibling get_current_rates (current values) and calculate_* tools.

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?

Conveys that this is for historical series with date-range filtering and periodic aggregation to reduce volume. It does not explicitly name alternatives like get_current_rates or say when NOT to use it, but the historical scope is clear.

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

All FalaZuki Finance BR toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources