Skip to main content
Glama

Pechim — Preços, Ofertas e Histórico no Brasil

Buscar produto no Pechim

buscar_produto
Read-onlyIdempotent

Procura produtos que o Pechim acompanha pelo nome ou pelo código de barras (EAN). Devolve até 10 produtos com o melhor preço atual, a loja, quando o preço foi verificado, se está em queda de preço confirmada e o link da página no Pechim. Se não encontrar o que procura, oriente o usuário a cadastrar o link da loja ou pedir o produto em https://pechim.com.br. Para o histórico completo ("Esse preço está bom?"), use preco_de_produto.

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": {
      "consulta": "<consulta>"
    },
    "name": "buscar_produto"
  }
}

Input Schema

NameRequiredDescriptionDefault
consultaYesNome do produto (ex.: "iphone 15 128gb") ou código de barras com 8, 12, 13 ou 14 dígitos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint, idempotent, non-destructive), and the description goes well beyond them with behavior the agent needs: a hard cap of 10 results, the fields returned (melhor preço, loja, data de verificação, queda confirmada, link), and the fallback when nothing matches. No behavior is contradicted.

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?

Four short sentences, front-loaded with purpose, then return shape, then failure handling, then the sibling redirect. Nothing is redundant with the schema or the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description covers selection criteria, result count and composition, and the empty-result case — everything needed to invoke it and interpret it correctly.

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 100% and the single parameter already documents name-or-barcode usage plus the accepted digit counts. The description restates the same fact (nome ou código de barras/EAN) without adding format or parsing detail, so the baseline 3 applies.

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?

The description opens with a specific verb and resource ("Procura produtos") and states the lookup key (nome ou código de barras/EAN). It explicitly contrasts itself with the sibling preco_de_produto by reserving full price history for that tool, so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

It names the alternative tool and the exact condition that selects it ("Para o histórico completo ... use preco_de_produto"), and it also covers the zero-result path by instructing the agent to point the user to cadastrar o link da loja or pechim.com.br.

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