Skip to main content
Glama

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

Buscar VPN, gerenciador de senhas ou antivírus

buscar_produtos
Read-onlyIdempotent

Busca produtos de segurança digital por categoria (vpn, senhas, antivirus), texto livre, uso (streaming, familia, gratis, privacidade, iniciantes, torrent, viagem, celular, preco, empresas, codigo_aberto, pc_lento, completo, mac), só grátis e preço mensal máximo. Devolve preço mensal de referência, plano grátis, garantia e link 'comprar' do site oficial.

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
moedaNoOpcional: força a moeda dos preços
textoNoEx.: Netflix, Linux, família, sem logs
gratisNo
idiomaNoIdioma da resposta: pt (Brasil, preços em BRL) ou es (América Latina, preços em USD)
limiteNo1 a 30, padrão 10
categoriaNo
preco_mes_maxNoPreço mensal máximo na moeda da resposta

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so safety needs no further explanation. The description earns credit by disclosing the response payload — monthly reference price, free plan, guarantee, and an official "comprar" link — which matters because there is no output schema. It does not say where the data comes from or how stale prices may be.

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 dense sentence front-loads the verb and resource, then the filters, then the return values — the right order for an agent scanning the definition. The 15-value `uso` enumeration is long but each token is a distinct, usable filter value rather than filler.

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?

For an 8-parameter, all-optional search with no output schema, the description covers the filter surface and the return fields, which is what an agent needs to invoke and interpret it. Minor gaps: the interaction between `idioma`/`moeda` and the reported prices, and the default result count, are only in the schema.

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 63%, and the description compensates precisely where the schema is silent: it enumerates the 15 `uso` values (the schema gives `uso` no enum or description), restates the `categoria` options, and explains `gratis` and `preco_mes_max` in prose. It adds nothing for `moeda`, `idioma`, and `limite`, but those already carry schema descriptions, and it does not explain how `texto` free-text search interacts with the structured filters.

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 opens with a specific verb plus resource ("Busca produtos de segurança digital") and enumerates the three categories and the filter axes, so an agent immediately knows this is a catalog search. It does not name any sibling (comparar_produtos, melhores_para, ficha_produto), so the boundary between search and comparison/ranking is left 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?

The long list of `uso` values (streaming, familia, gratis, privacidade, torrent, viagem, celular, preco, empresas, codigo_aberto, pc_lento, completo, mac) implicitly tells the agent which scenarios this tool serves. However, there is no explicit when-to-use/when-not-to-use statement and no routing to siblings like comparar_produtos or ficha_produto for follow-up steps.

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