Skip to main content
Glama

ofertas_do_dia

Read-only

Ofertas com desconto REAL de hoje (desconto informado pela própria loja, nunca inventado), da Shopee e de lojas parceiras. Filtra por categoria e preço máximo. Use para "promoções de hoje", "ofertas de eletrônicos", "achadinhos até R$ 50".

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

Input Schema

NameRequiredDescriptionDefault
limiteNoPadrão 10, máximo 30.
categoriaNoOpcional. Uma de: Casa, Cozinha, Moda, Acessórios, Calçados, Beleza, Eletrônicos, Cama e banho, Ferramentas, Esporte, Escritório, Pet.
preco_maximoNoOpcional, em reais.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine provenance context — discounts come from the store itself and are never fabricated — plus the source scope (Shopee + partners), but says nothing about result ordering, pagination, or what an empty result means.

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?

Three short sentences, front-loaded with what the tool returns before the filter and usage details. The parenthetical about real discounts is slightly wordy but carries a trust signal that justifies its space.

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 zero-required-parameter read-only listing tool with annotations and a fully described schema, this covers purpose, sources, filters, and invocation triggers. Only return-shape and result-volume expectations are absent, and no output schema exists to fill that 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 coverage is 100% and all three optional parameters are documented in the schema, including the default/max limit and the allowed category values. The description only restates that categoria and preco_maximo act as filters, adding no format or edge-case meaning beyond 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?

Specific verb+resource: discounted offers of the day from Shopee and partner stores, with category and max-price filtering. It clearly separates itself from price-lookup siblings (buscar_preco, historico_preco) by being a curated deals listing, though it never names an alternative explicitly.

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?

Provides concrete trigger phrases ("promoções de hoje", "ofertas de eletrônicos", "achadinhos até R$ 50") that tell the agent when this tool fits. It lacks an explicit when-not / use-instead clause, so routing against siblings remains partly inferred.

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