Skip to main content
Glama

Cupons de desconto ativos

cupons_ativos
Read-onlyIdempotent

Lista cupons de desconto válidos das lojas parceiras do Pechim (Amazon, Mercado Livre, Magalu, Shopee, Casas Bahia, etc.), com código, regras, validade e link direto de ativação. Aceita filtro opcional por loja (ex.: "amazon", "shopee"). Use quando o usuário perguntar por cupons ou códigos promocionais.

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

Input Schema

NameRequiredDescriptionDefault
lojaNoNome ou domínio da loja para filtrar cupons (opcional, ex.: "amazon", "shopee", "magalu").

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value by enumerating the response content (code, rules, validity, direct activation link), which matters since there is no output schema. It omits any note on result volume or refresh frequency of coupon validity.

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 sentences, front-loaded with what the tool returns, followed by the optional filter and the usage trigger. No filler or redundant phrasing.

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?

For a single optional-parameter read tool with no output schema, the description covers purpose, returned fields, filtering, and the trigger condition. Nothing an agent needs to call it correctly is missing.

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 schema already documents 'loja' as name or domain with example values. The description only restates that the filter is optional with the same examples, adding no new matching semantics such as partial-match or case-insensitivity behavior. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lista cupons de desconto válidos') plus the partner stores covered and the data returned (código, regras, validade, link de ativação). This is clearly distinguishable from price, product-search, and best-offer siblings without opening any schema.

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 an explicit trigger: 'Use quando o usuário perguntar por cupons ou códigos promocionais.' It does not state when not to use it or name a sibling alternative (e.g., for general discounts vs. product prices), so it stops short of full routing guidance.

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