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

brasil-data-mcp

by alanpcf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

listar_taxas

Retrieve all current Brazilian economic rates (SELIC, CDI, IPCA) for a complete overview and comparison.

Instructions

Lista TODAS as taxas econômicas brasileiras disponíveis na BrasilAPI (SELIC, CDI, IPCA) com seus valores atuais. Retorna em JSON um array com nome e valor (% ao ano) de cada taxa. Use quando o usuário quiser um panorama econômico, comparar SELIC vs CDI vs IPCA, ou não souber a sigla específica. NÃO use quando o usuário já sabe qual taxa quer — use consultar_taxa que é semanticamente mais direto. Hoje são só 3 taxas; o payload é pequeno.

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": "listar_taxas"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations provided, so description carries full behavioral burden. It describes return format (JSON array with name and value), mentions payload size is small, and lists exactly 3 taxes. It doesn't mention any destructive actions (none expected). Could be improved by noting data source or update frequency, but adequate.

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?

Highly concise yet informative. Front-loaded with purpose, followed by usage guidance and return format. Every sentence adds value without redundancy.

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

Completeness5/5

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

Given no output schema, description explains the return structure (JSON array with name and value), lists the specific rates, and notes there are exactly 3. This is complete for a simple list tool.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has zero parameters, and schema coverage is 100% (vacuously). Baseline for zero-param tools is 4. The description doesn't need to add parameter info, and it correctly implies no user input is needed.

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?

Description clearly states the tool lists all Brazilian economic rates (SELIC, CDI, IPCA) with current values. It distinguishes itself from sibling consultar_taxa by noting it returns all rates vs a specific one.

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

Usage Guidelines5/5

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

Explicitly provides use cases: when user wants a panoramic view or doesn't know specific rate. Also states when NOT to use (when user knows specific rate) and directs to the sibling consultar_taxa.

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