Skip to main content
Glama

cloo.be: ofertas do Brasil

Detalhes da oferta

fetch
Read-onlyIdempotent

Detalhes de uma oferta pelo id (ou pela URL da página no cloo.be): preço atual, preço anterior, desconto, nota, vendas, loja, data da verificação e link de compra.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId da oferta exatamente como vem nas buscas, ou a URL https://cloo.be/ofertas/…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Id da oferta como vem nas buscas (Shopee: só dígitos; Mercado Livre: MLB…; AliExpress: AE…; Amazon: amazon:…; Magalu: magalu:…; Shein: shein:…) ou a URL https://cloo.be/ofertas/…"New value: +"Id da oferta exatamente como vem nas buscas, ou a URL https://cloo.be/ofertas/…"
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Id da oferta como vem nas buscas (Shopee: só dígitos; Mercado Livre: MLB…; AliExpress: AE…) ou a URL https://cloo.be/ofertas/…"New value: +"Id da oferta como vem nas buscas (Shopee: só dígitos; Mercado Livre: MLB…; AliExpress: AE…; Amazon: amazon:…; Magalu: magalu:…; Shein: shein:…) ou a URL https://cloo.be/ofertas/…"
  3. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Id da oferta (número) ou URL https://cloo.be/ofertas/…"New value: +"Id da oferta como vem nas buscas (Shopee: só dígitos; Mercado Livre: MLB…; AliExpress: AE…) ou a URL https://cloo.be/ofertas/…"
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the description adds value by enumerating the fields returned, which stands in for the absent output schema. It does not describe error behaviour for invalid/stale offers or whether prices are cached as of the stated verification date — a minor gap given annotations already signal a safe, idempotent read.

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?

One front-loaded sentence that leads with the resource and key, then lists payload fields — every clause carries information with no filler. It is dense but readable, and slightly long only because the field enumeration is doing the missing output-schema work.

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 one-parameter read tool with a fully documented schema and rich annotations, the description supplies what structured fields cannot: the shape of the returned offer data. Nothing essential for correct invocation is missing, though a note on behaviour for unknown/expired ids would complete it.

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 is fully documented in the schema, including the URL alternative ('ou a URL https://cloo.be/ofertas/…'). The description restates the id/URL duality without adding format rules, validation behaviour, or examples, so the high-coverage baseline of 3 applies.

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+resource ('Detalhes de uma oferta pelo id') plus the accepted alternative key (page URL), and enumerates the fields returned (price, previous price, discount, rating, sales, store, verification date, buy link). It is clearly a single-item lookup, which implicitly contrasts with the list/search siblings, but no sibling is named so the differentiation is not explicit.

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 only implied: an agent can infer this is the tool for a single offer once it already has an id or URL. There is no explicit statement of when to prefer it over buscar_ofertas or ofertas_da_categoria, and no exclusions or prerequisites (e.g. what happens with an expired or unknown id).

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.