Skip to main content
Glama

Melhores ofertas com quedas de preço no Pechim

melhores_ofertas
Read-onlyIdempotent

Lista os produtos com as maiores quedas de preço confirmadas pelo Pechim (baseado no histórico real, não em preços sugeridos). Suporta filtro opcional por termo de busca no nome do produto (ex.: "headset", "air fryer", "iphone"), filtro de categoria (ex.: "celulares", "televisores"), preço máximo em reais (ex.: 2000 para até R$ 2.000) e limite de resultados. Use para responder "o que está em promoção agora?", "quais são os maiores descontos hoje?", "ofertas de headset" ou "celulares em promoção até R$ 2000".

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": "melhores_ofertas"
  }
}

Input Schema

NameRequiredDescriptionDefault
termoNoTermo de busca para filtrar produtos pelo nome (ex.: "headset", "air fryer", "iphone", "tenis"). Omita para ver ofertas em geral.
limiteNoQuantidade de produtos (1 a 20). Padrão: 10.
categoriaNoSlug de categoria para filtrar (ex.: "celulares", "televisores"). Omita para ver todas as categorias.
preco_maximoNoPreço máximo em reais (ex.: 2000 para ofertas até R$ 2.000,00). Omita para ver ofertas de qualquer valor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / termo
      Added value: +{
      +  "description": "Termo de busca para filtrar produtos pelo nome (ex.: \"headset\", \"air fryer\", \"iphone\", \"tenis\"). Omita para ver ofertas em geral.",
      +  "maxLength": 80,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-redundant context: results are based on confirmed real price history rather than suggested prices, which tells the agent how much to trust the output. It does not disclose result ordering (presumably by drop size) or what fields each offer carries.

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?

Two sentences, purpose front-loaded, then filters, then use cases — a sensible progression with no filler. The repeated examples for termo and categoria overlap with the schema, which is the only mild waste.

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 read-only, four-optional-parameter listing tool with full annotation coverage, the description covers purpose, filters, and trigger questions adequately. With no output schema, a brief note on what each offer returns and how results are ordered would have closed the remaining gap.

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%, so every parameter already carries its own explanation and the description's per-parameter examples ("headset", "celulares", 2000 para R$ 2.000) largely restate them. Baseline 3 applies since the schema, not the description, does the semantic work.

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?

"Lista os produtos com as maiores quedas de preço" gives a specific verb plus resource and scopes the data source ("histórico real, não em preços sugeridos"), which separates it from a plain price-lookup or product-search tool. It stops short of naming a sibling as the alternative, so the differentiation is contextual rather than explicit.

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 final sentence enumerates four concrete user questions the tool answers ("o que está em promoção agora?", "maiores descontos hoje?", "ofertas de headset", "celulares em promoção até R$ 2000"), which is strong when-to-use guidance. It gives no when-not-to-use conditions and never points to preco_de_produto or buscar_produto for single-product lookups.

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