Skip to main content
Glama

Kit Viagem: travel insurance and currency exchange for Brazilian travelers

Comparar lado a lado

comparar_produtos
Read-onlyIdempotent

Compara de 2 a 4 seguros, contas ou eSIMs (ex.: Wise vs Nomad, Assist Card vs GTA, Airalo vs Holafly).

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": {
      "ids": "<ids>"
    },
    "name": "comparar_produtos"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and side-effect behavior are fully covered by structured data. The description adds nothing beyond that profile: with no output schema, it never says what a comparison actually returns (which fields, in what shape, or whether items missing from the catalog are reported).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

One sentence, front-loaded with the core action and constraint, followed by examples that resolve ambiguity without padding. Nothing is redundant or off-topic.

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?

The tool is simple (one array parameter, no nesting), and the description covers the operation and cardinality. But with no output schema and no parameter descriptions, the return contract and the source of the ids remain undocumented, which is the main missing piece an agent would need before calling.

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 the load; it does clarify that the values are product identifiers spanning several categories (seguros, contas, eSIMs) and restates the 2–4 count that minItems/maxItems already enforce. It still does not say where those ids come from (presumably buscar_produtos results) or whether order matters in the comparison.

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 states a specific verb and resource (compare 2–4 products) and narrows the domain with concrete examples ('Wise vs Nomad', 'Airalo vs Holafly'), so an agent immediately knows this produces a side-by-side comparison rather than a lookup. It does not explicitly name a sibling (e.g. ficha_produto) as the single-item alternative, which keeps it short of a 5.

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?

The quantity range (2 to 4) and the paired examples imply the multi-item scenario, so an agent can infer this is the tool for evaluating options against each other rather than fetching one record. However, there is no explicit statement of when to prefer this over buscar_produtos or ficha_produto, and no exclusions or 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