Skip to main content
Glama

Kit Viagem: travel insurance and currency exchange for Brazilian travelers

Seguro viagem para um destino

seguro_para_destino
Read-onlyIdempotent

Para um país de destino (ex.: Portugal, Estados Unidos, Argentina, Cuba, Japão): diz se o seguro é obrigatório para brasileiros, a cobertura mínima, visto, custo médico e dicas de dinheiro, e lista os seguros mais baratos (cotação de referência em reais) e as contas/cartões internacionais de menor custo.

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": {
      "destino": "<destino>"
    },
    "name": "seguro_para_destino"
  }
}

Input Schema

NameRequiredDescriptionDefault
idadeNoOpcional: faixa de idade do viajante, só para filtrar planos com limite de idade (não é armazenada)
destinoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idade / description
      Previous value: -"Idade do viajante (opcional)"New value: +"Opcional: faixa de idade do viajante, só para filtrar planos com limite de idade (não é armazenada)"
  2. 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 read-only, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful context that the insurance prices are 'cotação de referência em reais' rather than live bookable quotes, but says nothing about data freshness, coverage of destinations, or what happens for an unsupported country.

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 front-loaded sentence that names the input first and then the outputs; dense but no filler. The long enumerated output list is informative rather than redundant, though it could be split for easier scanning.

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?

With no output schema, the description must carry the return-value burden and does so thoroughly, listing each answer category the caller gets. Both parameters are accounted for; only secondary details such as data currency and unsupported-destination behavior are absent.

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 50%: 'idade' is already fully documented in the schema as an optional filter that is not stored, and 'destino' is undocumented there. The description compensates for 'destino' by clarifying it is a country and giving concrete examples, adding modest value but still no format rules for the string.

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: given a destination country, it reports whether travel insurance is mandatory for Brazilians plus related trip facts and cheapest options. The enumeration of what comes back (obligation, minimum coverage, visa, medical cost, cheapest insurance quotes, cheap international cards) makes the scope distinguishable from sibling product-comparison tools without opening the schema.

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 only implied by the opening 'Para um país de destino (ex.: Portugal, Estados Unidos...)', which tells the agent to pass a country rather than a product or category. There is no explicit when-to-use-versus-alternative guidance and no exclusions (e.g., when to use comparar_produtos instead).

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