Skip to main content
Glama

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

Melhores para um uso

melhores_para
Read-onlyIdempotent

Lista os produtos de uma categoria indicados para um uso (ex.: VPN para streaming, gerenciador de senhas para família, antivírus grátis), do menor para o maior preço mensal.

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": {
      "categoria": "<categoria>"
    },
    "name": "melhores_para"
  }
}

Input Schema

NameRequiredDescriptionDefault
usoNostreaming, familia, gratis, privacidade, iniciantes, torrent, viagem, celular, preco, empresas, codigo_aberto, pc_lento, completo, mac
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)
limiteNo
categoriaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 safety is covered. The description adds real behavioral detail beyond them: results are restricted to use-case matches and sorted ascending by monthly price. It omits how many results come back, whether a default limit applies, and what happens with unsupported categoria/uso combos.

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 with the core action first, the use-case qualifier second, and the ordering guarantee last. The parenthetical examples earn their place by disambiguating 'uso', and there is no filler.

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 no output schema and an annotation-only safety profile, the description does convey the population (products in a category) and ordering (cheapest monthly price first), which is the key return characteristic. It leaves open result cardinality and default limit behavior, which matter for a listing tool with a 'limite' parameter.

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 60% and three parameters carry enums, so the schema does most of the work. The description adds meaning by linking 'uso' to 'categoria' conceptually (use-case suitability within a category) and by examples that clarify the kind of values 'uso' accepts, but the undocumented 'limite' parameter is not addressed at all.

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?

States a concrete verb ('Lista'), a concrete resource ('produtos de uma categoria') and a concrete filter/ordering ('indicados para um uso', 'do menor para o maior preço mensal'). An agent can distinguish this from buscar_produtos or comparar_produtos by the use-case matching and price ordering, though no sibling is named explicitly.

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?

Usage is implied through the examples ('VPN para streaming, gerenciador de senhas para família, antivírus grátis'), which shows the sort of request this satisfies, but there is no explicit when-to-use vs when-not guidance and no sibling alternative is named for a plain lookup.

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