Skip to main content
Glama

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

Ficha completa de um produto

ficha_produto
Read-onlyIdempotent

Todos os dados de um produto: planos e preços (BRL/USD) com data e fonte, dispositivos, garantia, auditorias, testes independentes, incidentes conhecidos, 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.: nordvpn, bitwarden, bitdefender
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

B3.2/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 the safety profile needs no restating. With no output schema, the enumeration of returned data (prices with date and source, incidents, buy link) usefully signals what comes back, but nothing is said about behavior for unknown ids, price staleness assumptions, or response size.

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 that leads with the scope and then lists contents, with no filler or marketing language. The long comma-separated enumeration is dense but every item earns its place as a returned field, since there is no output schema.

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 a simple one-required-param read tool with full schema coverage and no output schema, the description is largely sufficient: it conveys the payload scope and currency dimension. The remaining gap is decision support — an agent still cannot tell from the description alone when to prefer this over buscar_produtos or comparar_produtos.

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 100% with enum values and descriptions for id, moeda, and idioma, so the schema already does the heavy lifting. The description only implicitly touches parameters by mentioning BRL/USD prices, adding no format or precedence detail (e.g., whether moeda overrides the idioma default) beyond the schema.

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 (all data for one product) and enumerates the concrete payload: plans/prices in BRL and USD with date and source, devices, warranty, audits, tests, incidents, pros/cons, and a buy link. It is clearly a single-product detail lookup, distinguishable from siblings like comparar_produtos or buscar_produtos, though it never names them.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the alternative tools (buscar_produtos for finding an id, comparar_produtos for multi-product comparison, alternativas/melhores_para for recommendations). The detail-oriented field list implies a lookup use case, but routing between siblings is left entirely to the agent's inference.

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