Skip to main content
Glama

List coupons for a deal

list_deal_coupons
Read-only

Active coupon codes of the store selling a deal, to check whether one applies to it. Each coupon title states its rule (discount, eligible products or brands, minimum purchase) and valid_until is the end date the store reports: compare them with the deal's title and price before suggesting a code. Content in Brazilian Portuguese.

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

Input Schema

NameRequiredDescriptionDefault
idYesDeal id, the UUID in https://pechincha.ai/p/<id>/<slug>

Output Schema

NameRequiredDescriptionDefault
dealYesnull when the deal does not exist
storeYes
totalYes
couponsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot: the content is in Brazilian Portuguese, coupon titles encode the rule, and valid_until is the store-reported end date rather than a guaranteed expiry.

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 tightly packed sentences, front-loaded with what is returned and then how to interpret it. No filler, though the language note could sit more naturally at the end.

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?

With an output schema present, return values need no explanation, and the description covers the semantic gotchas an agent needs: locale, title-encoded rules, and store-reported validity. Missing only an explicit pointer to the sibling tools for the non-deal case.

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?

There is only one parameter and schema description coverage is 100%, with the schema already explaining the deal UUID. The description adds no additional parameter meaning, so the baseline 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?

The description states a specific resource (active coupon codes) scoped to the store selling a given deal, and gives the reason for retrieval (to check applicability). It is distinguishable from siblings like list_store_coupons by the deal-scoped input, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent what to do with the results ('compare them with the deal's title and price before suggesting a code'), which implies the use case, but it never states when to prefer this over list_store_coupons or list_coupon_stores, nor any exclusion conditions.

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