Skip to main content
Glama

cloo.be: ofertas do Brasil

Buscar ofertas com filtros

buscar_ofertas
Read-onlyIdempotent

Busca ofertas das principais lojas e marketplaces do Brasil com filtros de preço máximo e desconto mínimo, ordenadas por relevância, mais vendidos, menor preço ou maior desconto. Para uma loja só, ponha o nome dela no termo (ex.: "air fryer" + nome da loja). Cada oferta traz a loja dela (store_name).

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": {
      "termo": "<termo>"
    },
    "name": "buscar_ofertas"
  }
}

Input Schema

NameRequiredDescriptionDefault
ordemNoOrdem dos resultados: relevância, mais vendidos, menor preço ou maior desconto.relevancia
termoYesNome do produto em 1 a 3 palavras, em português (ex.: "air fryer", "brinquedo infantil"). Frases como "melhor fone até 200 reais" também funcionam: o preço vira preco_maximo.
limiteNoQuantas ofertas devolver (1 a 20).
paginaNoPágina dos resultados (1 a 5), de "limite" em "limite". Use proxima_pagina da resposta anterior.
preco_maximoNoPreço máximo em reais.
desconto_minimoNoDesconto mínimo em %.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ordem / description
      Added value: +"Ordem dos resultados: relevância, mais vendidos, menor preço ou maior desconto."
  2. Changed1 schema field changed
    • addedInput schema / properties / pagina
      Added value: +{
      +  "default": 1,
      +  "description": "Página dos resultados (1 a 5), de \"limite\" em \"limite\". Use proxima_pagina da resposta anterior.",
      +  "maximum": 5,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / termo / description
      Previous value: -"Produto procurado, em português."New value: +"Nome do produto em 1 a 3 palavras, em português (ex.: \"air fryer\", \"brinquedo infantil\"). Frases como \"melhor fone até 200 reais\" também funcionam: o preço vira preco_maximo."
  4. First observed

TDQS

A3.7/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, so safety behavior needs no restating. The description adds one return-content fact (each offer carries store_name) and notes results are paginated only implicitly; it does not cover rate limits, empty-result behavior, or how pagination resumes, leaving gaps for a tool with no output schema.

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?

Three short sentences, front-loaded with what the tool does and its filtering/ordering scope, followed by the single-store tip and the store_name note. No filler or redundancy.

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 6-parameter search tool with full schema descriptions and no output schema, the description covers purpose, ordering dimension, filter capability, store scoping, and one returned field. It stops short of describing result shape or pagination continuation, which the agent would otherwise need.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, but the description adds meaning the schema does not: it explains that a single-store search is achieved by appending the store name to termo (e.g. "air fryer" + store name), and it clarifies that store_name is what comes back. That is genuine routing/value beyond the enum and price-filter definitions.

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 specific verb and resource ("Busca ofertas") plus scope ("principais lojas e marketplaces do Brasil") and filter capabilities, so the agent knows exactly what it returns. It does not explicitly distinguish itself from siblings such as ofertas_da_categoria or ofertas_em_alta, which keeps it from a 5.

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 by the filter/ordering framing, and there is one concrete tip: to target a single store, put the store name in the termo. However, there is no explicit when-to-use versus when-not guidance and no named alternative for category browsing or trending offers, so the agent must infer routing.

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.