Skip to main content
Glama

get_ptax_rate

Fetch official PTAX USD/BRL buy and sell rates for a given day to support currency conversion and financial reporting. Defaults to today; weekends and holidays have no quote.

Instructions

Return the official PTAX USD/BRL buy and sell rates for a day.

Args: day: Date in YYYY-MM-DD format. Defaults to today. Weekends and holidays have no quote.

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_ptax_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses that the source is official PTAX, that both buy and sell rates are returned, that 'day' defaults to today, and crucially that weekends/holidays produce no quote. It does not mention rate limits, caching, or the response shape.

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?

Front-loaded with the core action in the first sentence, followed by a compact Args block. Every sentence adds information (format, default, no-quote condition); nothing is 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-parameter read tool with no output schema, the description is nearly complete: the action, the parameter semantics, and the empty-result condition are all covered. The only gap is that the return structure (field names for buy/sell) is not described, which matters slightly without an output schema.

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 description coverage is 0%, so the description must compensate, and it does: it specifies the YYYY-MM-DD format, the default of today, and the null-result condition for non-business days. That is the meaningful information an agent needs for the single optional 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?

States a specific verb and resource: 'Return the official PTAX USD/BRL buy and sell rates'. The scope (official PTAX, USD/BRL pair, daily) is unambiguous, though it doesn't explicitly contrast with siblings like get_selic_rate.

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 by the domain rather than stated: fetch the exchange rate for a day. The note that weekends and holidays have no quote tells the agent when a call may come back empty, but there is no explicit guidance on when to prefer this over other rate tools or what to do on a no-quote day.

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