Skip to main content
Glama

ptax

Read-onlyIdempotent

Retrieves official Banco Central do Brasil closing exchange-rate quotes (buy and sell, BRL per currency) for a chosen currency over a date range or recent business days.

Instructions

Cotações PTAX de fechamento do Banco Central (compra e venda, em reais por unidade da moeda).

Args: moeda: símbolo da moeda (USD, EUR, GBP, JPY, CHF...). Use "lista" para ver as moedas disponíveis. inicio: data inicial (AAAA-MM-DD ou AAAA-MM). fim: data final; padrão: hoje. ultimos: quantidade de dias úteis mais recentes quando não há inicio.

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

Input Schema

NameRequiredDescriptionDefault
fimNo
moedaNoUSD
inicioNo
ultimosNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and idempotent behavior, so the bar is lower; the description still adds real value by specifying that these are closing rates (fechamento), buy and sell quotes, and that both sides are reported in reais per currency unit. Defaults for the end date and the recent-business-days fallback are also disclosed, though the return format and any rate limits are not.

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?

The identifying sentence is front-loaded, followed by a structured Args block with one line per parameter; there is no filler text. The purpose sentence is somewhat dense with parenthetical detail, but nothing is wasted.

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?

There is no output schema, so the description must carry return semantics; it does so by naming the closing PTAX buy and sell quotes and their unit. Combined with full parameter documentation, this is nearly complete, though the row-level shape of the returned series is not described.

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?

With schema description coverage at 0%, the description compensates well by documenting all four parameters: the currency symbol with an explicit child-tool escape hatch ('lista' lists available currencies), the accepted date formats (AAAA-MM-DD or AAAA-MM), the default end date of today, and the interaction where 'ultimos' governs the recent business-day window only when 'inicio' is omitted. Only the default value of 'ultimos' is left implicit.

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 resource and verb: PTAX closing quotes from Banco Central, with buy and sell rates expressed in reais per unit of currency. It is far more precise than the name 'ptax' alone, but it never distinguishes itself from sibling series tools that could also return exchange-rate data.

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 implied rather than stated: the agent can infer it fetches closing PTAX rates for a currency over a date range. There is a useful operational rule that 'ultimos' applies when 'inicio' is absent, but no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives.

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