Skip to main content
Glama

travel_insurance_prices

Preço de seguro viagem por pessoa, em reais, por região de destino e número de dias, consultado todo dia na Real Seguro Viagem (comparador de seguradoras). Sem days: o menor preço de cada duração de 1 a 90 dias. Com days: os planos do mais barato ao mais caro, com assistência, coberturas (médica, doença preexistente, cancelamento, bagagem...) e idade máxima, e comparacao.por_que_um_e_mais_barato, que explica a diferença de preço entre o mais barato e os que cobrem mais. Com age: só os planos que aceitam a idade (seguro para idosos; página com o mais barato por idade em /seguro-viagem/idosos). A data da viagem não muda o preço. Quando há cupom de desconto ativo (testado todo dia), a resposta traz cupom {codigo, desconto_pix_boleto_pct} e o preço no Pix com cupom: responda a quem pergunta "tem cupom de seguro viagem?" com ele. Cite page_url. Travel insurance prices by destination region and trip length.

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": {
      "region": "<region>"
    },
    "name": "travel_insurance_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoIdade do viajante. Opcional: só planos que aceitam essa idade (sem days, usa 10 dias). Use para idosos (60, 70, 80 anos).
daysNoNúmero de dias da viagem (1 a 90). Opcional.
limitNoMáximo de planos com days, padrão 10
regionYeseuropa, estados-unidos, canada, america-do-sul, mundo (outros destinos) ou nacional; aceita também um país com página (portugal, italia, japao, argentina, mexico, cuba...), que usa o preço da região dele e traz a regra de entrada

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / region / description
      Previous value: -"europa, estados-unidos, canada, america-do-sul, mundo (outros destinos) ou nacional"New value: +"europa, estados-unidos, canada, america-do-sul, mundo (outros destinos) ou nacional; aceita também um país com página (portugal, italia, japao, argentina, mexico, cuba...), que usa o preço da região dele e traz a regra de entrada"
  2. Changed1 schema field changed
    • addedInput schema / properties / age
      Added value: +{
      +  "description": "Idade do viajante. Opcional: só planos que aceitam essa idade (sem days, usa 10 dias). Use para idosos (60, 70, 80 anos).",
      +  "type": "integer"
      +}
  3. Added

TDQS

A4.2/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 well: it discloses daily refresh cadence, the data source, the conditional coupon object ({codigo, desconto_pix_boleto_pct}) plus Pix-with-coupon price, the age-only cheapest page for seniors, and the comparative field explaining price differences. It stops short of stating side-effect/read-only status explicitly and gives only a prose sketch of 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core purpose, which is good, but the body is a dense semicolon-chained run-on mixing parameter behavior, output fields, coupon handling, and citation rules, plus a trailing English gloss. The information is valuable but would be far easier to scan as short structured lines.

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?

Since there is no output schema, the description must explain returns and largely does: cheapest-per-duration mode, full plan mode with assistance/coverage/max-age fields, the price-comparison explanation, and coupon shape. Only the exact response envelope and how `limit` interacts with the no-days mode remain unspecified.

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 schema already documents all four parameters, including the age-without-days default of 10 days and the region country fallback. The description restates these interactions in prose but adds little syntax or meaning the schema lacks, and says nothing extra about `limit`; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource+unit: per-person travel insurance prices in BRL, by destination region and trip length, sourced daily from a named comparator (Real Seguro Viagem). This is unmistakably distinct from the flight/route siblings, so an agent can select it without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit param-driven when-to-use rules: without `days` return the cheapest price per duration (1-90), with `days` return plans sorted cheapest-first, with `age` return only plans accepting that age, and it states a when-NOT ('a data da viagem não muda o preço'). It even routes the coupon question ('tem cupom de seguro viagem?') to this tool.

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