Skip to main content
Glama

get_selic_rate

Retrieve Banco Central Selic target rate values (% per year) and specify how many recent entries to return.

Instructions

Return the latest Selic target rate values (% per year) from Banco Central.

Args: last: How many of the most recent values to return (1 to 20).

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

Input Schema

NameRequiredDescriptionDefault
lastNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does disclose the source and the unit, which matters for trusting the data. However, it says nothing about the shape of each returned value (e.g. whether a date accompanies each rate), pagination-like limits, or what happens if 'last' exceeds 20.

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 plus a compact Args block; purpose and unit come first, then the parameter. Nothing redundant.

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-parameter read-only tool with no output schema, the description covers purpose, unit, source, and the parameter's meaning and bounds. The remaining gap is the return structure and out-of-range behavior, which is modest but real.

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 0%, so the description must compensate, and it does: it explains that 'last' means how many of the most recent values to return and adds the valid range 1 to 20, which is absent from the schema. It stops short of stating default behavior or out-of-range handling.

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?

States a specific verb and resource ('Return the latest Selic target rate values') plus the unit (% per year) and the data source (Banco Central). The resource is specific enough to separate it from siblings like get_ptax_rate or get_ipca, though the description never explicitly contrasts them.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as get_ipca for inflation or get_ptax_rate for exchange rates. The only contextual cue is the implied 'latest values' use case.

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