Skip to main content
Glama

cloo.be: ofertas do Brasil

Pesquisar ofertas

search
Read-onlyIdempotent

Pesquisa ofertas das principais lojas e marketplaces do Brasil por produto (ex.: "air fryer", "fone bluetooth"). Mande o nome do produto em 1 a 3 palavras; "até R$ 200" na frase vira preço máximo. Para uma loja só, ponha o nome dela no termo (ex.: "air fryer" + nome da loja). Cada oferta traz a loja dela (store_name). Devolve id, título com preço e a página de cada oferta no cloo.be. Use fetch com o id para os detalhes.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesO que a pessoa procura, em português.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world behavior, so the description's added value is its disclosure that each result carries store_name plus id, priced title, and cloobe page URL. It also tells the agent to call `fetch` with the id for details, which is useful workflow context. It doesn't mention result limits, pagination, or empty-result behavior.

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?

Four short sentences, front-loaded with purpose then query format then result shape then next step. Every sentence carries information, with only slight redundancy between the store_name mention and the returned-fields sentence.

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?

There's no output schema, so the description correctly explains the return shape (id, priced title, page URL, store_name) and the follow-up `fetch` call. Combined with annotations covering safety, an agent has everything needed to call it correctly, with only pagination/limits left unstated.

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

Parameters5/5

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

Schema coverage is 100%, but the description goes well beyond the schema's generic 'what the person is looking for, in Portuguese'. It specifies the 1–3 word form, that 'até R$ 200' inside the phrase becomes a max price, and how to scope to a single store — real parsing semantics an agent could not infer from 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?

States a specific verb and resource (search offers from major Brazilian stores/marketplaces by product) with concrete query examples like 'air fryer' and 'fone bluetooth'. It explicitly routes the agent to `fetch` for details, though it doesn't clarify how it differs from sibling `buscar_ofertas` or `ofertas_da_categoria`.

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?

Gives clear usage context: send a short product name, how to express a max price ('até R$ 200'), and how to narrow to one store by including the store name in the term. It also names `fetch` as the follow-up step. It doesn't state when not to use this versus the other offer-listing siblings.

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.