Skip to main content
Glama

Kit Viagem: travel insurance and currency exchange for Brazilian travelers

Ficha completa

ficha_produto
Read-onlyIdempotent

Todos os dados de um seguro, conta ou eSIM (ex.: airalo, holafly): planos, preços com data e fonte, coberturas ou tarifas, pontos fortes e fracos e link 'comprar'.

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": {
      "id": "<id>"
    },
    "name": "ficha_produto"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid ou nome, ex.: assist-card, wise, nomad

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description goes beyond them by disclosing the payload composition, notably that prices carry a date and a source (a freshness/attribution cue) and that pros/cons and a purchase link are included, which helps an agent decide whether the call answers the user's question.

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?

One front-loaded sentence: the scope ('todos os dados de um seguro, conta ou eSIM') comes first, followed by the concrete field list, with examples in parentheses. No filler, though the list is dense and could have used a short verb phrase to anchor it.

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 carries the burden of telling the agent what comes back, and it does so item by item. Annotations cover the safety profile and the schema covers the parameter, so the only remaining gap is failure behavior (unknown id) and result size.

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?

Single parameter with 100% schema description coverage, so the schema already explains that 'id' accepts an id or a name and gives examples (assist-card, wise, nomad). The description adds no further meaning about the identifier format or matching behavior; baseline 3 applies.

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 resource precisely (full record for one insurance/account/eSIM product) and enumerates the payload: plans, prices with date and source, coverages/rates, pros and cons, buy link. That is clearly distinguishable from search/compare-style siblings, though no sibling is named explicitly and there is no leading verb such as 'retorna'/'obtém'.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use statement. An agent must infer that this is the single-product detail lookup to be used after buscar_produtos or instead of comparar_produtos; nothing in the text routes it against those siblings or states prerequisites.

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