Skip to main content
Glama

Consultar taxas (Selic, CDI, IPCA)

consultar_taxas
Read-onlyIdempotent

Retrieve current Brazilian reference rates (Selic, CDI, IPCA) in annual percentage; omit the acronym to return all three.

Instructions

Retorna o valor atual das taxas de referência (Selic, CDI e IPCA, em % ao ano). Sem sigla, retorna todas.

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

Input Schema

NameRequiredDescriptionDefault
siglaNoTaxa específica (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds real context beyond that: the values are 'atuais' (current), expressed as % ao ano, and omitting the parameter returns all three. It says nothing about data freshness, source, or response shape, which would be valuable given openWorldHint=true.

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 short sentences with zero filler. The resource and unit are front-loaded, and the default-behavior rule follows immediately after; every clause earns its place.

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 single-optional-enum read tool with no output schema, the description covers what is returned, in what unit, and what happens with no argument. Only the provenance/freshness of the open-world data is unaddressed, a minor gap at this complexity.

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?

Schema coverage is 100% and the enum is self-documenting, so the baseline would be 3. The description goes beyond the schema by explaining the outcome of omitting 'sigla' (returns all rates), which the schema only marks as optional — that is genuine added meaning for the only parameter.

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 states a specific verb and resource ('Retorna o valor atual das taxas de referência') and enumerates exactly what is returned (Selic, CDI, IPCA), including the unit (% ao ano). Siblings cover entirely unrelated resources (CEP, CNPJ, ISBN), so no disambiguation is needed; it stops short of an explicit contrast, hence 4.

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?

The clause 'Sem sigla, retorna todas' gives a concrete rule for the no-argument case, which is useful usage guidance for a single optional-parameter tool. There is no explicit when-to-use/when-not framing or named alternative, but the tool's scope is narrow enough that none is really needed.

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