Skip to main content
Glama

Kit Viagem: travel insurance and currency exchange for Brazilian travelers

Buscar seguros, contas internacionais ou eSIM

buscar_produtos
Read-onlyIdempotent

Busca seguros viagem, contas/cartões/câmbio ou eSIM/chip internacional por categoria (seguro, cambio, esim), texto livre, uso (europa, eua, america_sul, argentina, ilimitado...) e preço máximo em reais.

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

Input Schema

NameRequiredDescriptionDefault
usoNo
textoNo
limiteNo
categoriaNo
preco_maxNo

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

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavior beyond that: it does not say whether an empty query returns everything, how results are ordered or capped, or what a result record contains. With annotations doing the safety work, the description's failure to add any operational context is a real gap.

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 starts with the verb and resource and then stacks the filter axes in a logical order. Dense but every clause carries a distinct filter; only the parenthetical example list in 'uso' pushes it toward over-packing.

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?

With five optional parameters, no output schema, and zero schema descriptions, the description needs to explain both filtering and what comes back. It covers filtering reasonably but says nothing about the return shape or result count, and leaves 'limete' undefined, so an agent can invoke it but cannot predict the response.

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 must carry all five parameters. It successfully explains four — categoria with the three enum values, texto as free text, uso with concrete example values (europa, eua, america_sul, argentina, ilimitado), and preco_max as a ceiling in reais — but 'limete' (integer) is never mentioned and its meaning versus preco_max is ambiguous. Good compensation, 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 a specific verb ('Busca') and enumerates the exact resource set — travel insurance, international accounts/cards/FX, and eSIM/chip — plus the filter dimensions. An agent can tell it is the catalog search tool, though it never names a sibling (e.g. comparar_produtos or melhores_para) to contrast against, so differentiation is only implicit.

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?

It implies usage by listing the filter axes (categoria, texto livre, uso, preço máximo), which suggests 'use this to find products matching these attributes'. But there is no explicit when-to-use, no when-not-to-use, and no routing to the sibling comparison or per-destination tools, so the agent must infer the boundary itself.

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