Skip to main content
Glama

cloo.be: ofertas do Brasil

Ofertas por categoria

ofertas_da_categoria
Read-onlyIdempotent

Melhores ofertas de uma categoria (ex.: casa-e-decoracao, beleza, celulares-e-acessorios), por maior desconto ou mais vendidos, com preço máximo opcional.

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": {
      "categoria": "<categoria>"
    },
    "name": "ofertas_da_categoria"
  }
}

Input Schema

NameRequiredDescriptionDefault
ordemNoOrdem dos resultados: maior desconto ou mais vendidos.desconto
limiteNoQuantas ofertas devolver (1 a 20).
paginaNoPágina dos resultados (1 a 5), de "limite" em "limite". Use proxima_pagina da resposta anterior.
categoriaYesCategoria das ofertas, pelo identificador da lista (ex.: casa-e-decoracao, beleza).
preco_maximoNoPreço máximo em reais.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / categoria / description
      Added value: +"Categoria das ofertas, pelo identificador da lista (ex.: casa-e-decoracao, beleza)."
    • addedInput schema / properties / ordem / description
      Added value: +"Ordem dos resultados: maior desconto ou mais vendidos."
  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. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds that results are ranked 'por maior desconto ou mais vendidos', which is useful behavioral context, but says nothing about result shape, whether offers are deduplicated, or how empty categories behave.

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 sentence that front-loads the core resource and scope, then compactly layers the sorting dimension and optional filter. No filler, though the inline example list of three slugs is slightly verbose for what the enum already provides.

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

Completeness3/5

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

All parameters are covered by a rich schema, and there is no output schema, so the description arguably should explain what an 'oferta' contains (price, discount, store, link). That gap plus the absence of pagination guidance leaves it adequate rather than complete.

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 all five parameters are already documented in the schema, giving a baseline of 3. The description reinforces the category identifier with example slugs and restates the ordering and price-cap semantics, but adds no new meaning and never mentions limite or pagina.

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 resource (ofertas) scoped to one category, and names the two ranking modes and the optional price cap. It is clear what the tool returns, but it never mentions the sibling buscar_ofertas, so the agent cannot distinguish the two tools from the description alone.

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: 'melhores ofertas de uma categoria' plus example category slugs tells the agent this is a per-category top-offers listing. There is no explicit when-to-use vs when-not guidance and no named alternative for broader or keyword-based searches.

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.