Skip to main content
Glama

Escudo Compara: VPN, password managers and antivirus (Brazil and Latin America)

Comparar produtos lado a lado

comparar_produtos
Read-onlyIdempotent

Compara de 2 a 4 produtos (ex.: NordVPN vs Surfshark) em preço, plano grátis, garantia, dispositivos, auditoria, incidentes e recursos, e diz qual é o mais barato.

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
moedaNoOpcional: força a moeda dos preços
idiomaNoIdioma da resposta: pt (Brasil, preços em BRL) ou es (América Latina, preços em USD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds real value beyond them by disclosing the comparison dimensions covered and that a cheapest-price verdict is returned — behavior an agent could not infer from the annotations. It does not cover failure modes (e.g. invalid or unknown ids) or result ordering.

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?

A single front-loaded sentence: verb and arity first, then the compared attributes, then the output verdict. Every clause carries information and nothing is repeated from the schema or annotations.

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 hint at the return value, and it does by naming the compared fields and the cheapest-product verdict. For a three-parameter read-only tool this is nearly sufficient; only the id format and error handling remain unstated.

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 67% and moeda/idioma already carry their own enum descriptions, including the pt/BRL vs es/USD coupling. The description only reinforces the 2-4 count already encoded in minItems/maxItems and never explains what an id looks like (slug, numeric, name), which is the one genuinely undocumented aspect. Baseline 3 is appropriate given the schema does most of the work.

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 specific verb (compara) plus the resource (2 a 4 produtos) and enumerates exactly what is compared — preço, plano grátis, garantia, dispositivos, auditoria, incidentes e recursos — plus the verdict it produces ('diz qual é o mais barato'). This is clearly distinct from siblings like buscar_produtos or ficha_produto, which imply search and single-product detail.

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

Usage Guidelines4/5

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

The 2-to-4 product range and the 'NordVPN vs Surfshark' example make the intended scenario unambiguous, so an agent knows this is the multi-product comparison path. It stops short of naming an alternative for the single-product or free-text-search cases (e.g. ficha_produto, buscar_produtos), so there is context but no explicit exclusion.

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