Skip to main content
Glama

Kit Viagem: travel insurance and currency exchange for Brazilian travelers

Melhores para um uso

melhores_para
Read-onlyIdempotent

Seguros, contas ou eSIMs indicados para um uso (europa, eua, america_sul, argentina, ilimitado, intercambio, mochilao, cruzeiro, familia; viagem_curta, morar_fora, enviar_dinheiro...). Para eSIM (categoria esim) com uso europa, eua ou america_sul, ordena pelo preço do pacote de 7 dias ilimitado.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "categoria": "<categoria>"
    },
    "name": "melhores_para"
  }
}

Input Schema

NameRequiredDescriptionDefault
usoNo
limiteNo
categoriaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / categoria / enum
      Previous value: -[
      -  "seguro",
      -  "cambio"
      -]New value: +[
      +  "seguro",
      +  "cambio",
      +  "esim"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, closed-world query, so the safety bar is low. The description adds real behavioral context beyond that: for categoria=esim with europa/eua/america_sul it orders results by the price of the 7-day unlimited package, which an agent could not infer from structured fields.

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?

Two sentences with no filler; the resource list and use-case vocabulary come first, followed by the eSIM sorting rule. The long parenthetical value list is dense but each item is functional information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with annotations and no output schema, most of what an agent needs is present, including the crucial `uso` vocabulary. Gaps remain around `limite` (what it limits and its default) and the general result ordering for non-eSIM categories.

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 description coverage is 0%, so the description carries the burden. It usefully enumerates the accepted `uso` strings, which compensates for the free-form string with no enum. However, `limite` is never mentioned, and `categoria` values are only partially discussed (esim is explained, seguro/cambio are not), so compensation is incomplete.

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 names the returned resources (seguros, contas, eSIMs) and the concept of ranking them by a use case, which is more specific than the title alone. It does not explicitly contrast itself with siblings such as buscar_produtos or seguro_para_destino, so an agent must infer the boundary.

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 through the enumerated `uso` values (europa, eua, intercambio, mochilao...) and one explicit rule for eSIM with europa/eua/america_sul. There is no statement of when to prefer this over buscar_produtos or seguro_para_destino, and no exclusion guidance.

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