Skip to main content
Glama

Kit Viagem: travel insurance and currency exchange for Brazilian travelers

Custo de gastar dinheiro no exterior

custo_cambio
Read-onlyIdempotent

Ranking de contas globais, cartões e serviços de câmbio (Wise, Nomad, C6, Inter, cartão de crédito comum, dinheiro em espécie...) pelo custo estimado para gastar um valor em dólares no exterior, com IOF e spread.

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

Input Schema

NameRequiredDescriptionDefault
usoNoviagem_curta, morar_fora, intercambio, enviar_dinheiro, varias_moedas, investir_dolar, receber_do_exterior
valor_usdNoValor a gastar em US$ (padrão 1000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that values are estimates and that IOF and spread are factored in, which is useful context, but it says nothing about data freshness, provider coverage limits, or how the ranking is ordered beyond 'custo estimado'.

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?

A single dense sentence that front-loads the deliverable (ranking) and then the criterion (cost with IOF and spread). The parenthetical provider list earns its place by defining scope, though the sentence is long and could be split for readability.

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 read-only, closed-world, two-parameter ranking tool with no output schema, the description conveys enough to call it correctly and anticipate the return shape (an ordered list of providers by cost). Only the role of the 'uso' profile and the assumption behind the cost estimate are left implicit.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description does not mention either parameter; notably it never explains that 'uso' (viagem_curta, morar_fora, investir_dolar, etc.) reshapes the ranking, and the schema only lists enum values without defining them, so a small gap remains.

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?

Description states a specific verb+resource: it returns a ranking of global accounts, cards and exchange services by estimated cost for spending dollars abroad, including IOF and spread. Named providers (Wise, Nomad, C6, Inter, credit card, cash) make the scope concrete. It does not explicitly distinguish itself from siblings like comparar_produtos or melhores_para, so it falls short of a 5.

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 resource ('gastar um valor em dólares no exterior'), but there is no explicit when-to-use, no exclusion of alternatives such as comparar_produtos, and no mention of when the result is not appropriate (e.g., domestic spending or remittances).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources