Skip to main content
Glama

CardDeals Live Gift Card Deals

Look up multiple gift-card brands

lookup_gift_card_deals
Read-onlyIdempotent

Use this when the user supplies up to 10 exact CardDeals product IDs or brand slugs to compare in one call. Product IDs use the form brand:starbucks. Do not use it for fuzzy discovery; use search_gift_card_deals instead. Unknown IDs are returned in not_found instead of being guessed.

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": {
      "ids": "<ids>"
    },
    "name": "lookup_gift_card_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesCardDeals product IDs or exact brand slugs.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
currencyYes
productsYes
not_foundYes
schema_versionYes
freshness_noticeYes
affiliate_disclosureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedOutput schema / properties / products / items / properties / base_domain / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / products / items / properties / base_domain / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / products / items / properties / deals / items / properties / fetched_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / products / items / properties / deals / items / properties / fetched_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / products / items / properties / deals / items / properties / variant / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / products / items / properties / deals / items / properties / variant / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / products / items / properties / deals / items / properties / variant_label / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / products / items / properties / deals / items / properties / variant_label / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / products / items / properties / deals / items / properties / id_verification_required
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / products / items / properties / deals / items / required
      Previous value: -[
      -  "deal_id",
      -  "provider_name",
      -  "provider_slug",
      -  "discount_percent",
      -  "in_stock",
      -  "fetched_at",
      -  "purchase_url",
      -  "variant",
      -  "variant_label",
      -  "coupon",
      -  "conditions",
      -  "seller_terms",
      -  "relationship",
      -  "disclosure"
      -]New value: +[
      +  "deal_id",
      +  "provider_name",
      +  "provider_slug",
      +  "discount_percent",
      +  "in_stock",
      +  "fetched_at",
      +  "purchase_url",
      +  "variant",
      +  "variant_label",
      +  "coupon",
      +  "conditions",
      +  "seller_terms",
      +  "relationship",
      +  "disclosure",
      +  "id_verification_required"
      +]
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

While annotations cover read-only status, the description adds crucial behavioral traits regarding execution. Specifically, it discloses that unknown IDs will be returned in a 'not_found' status rather than being 'guessed' or silently failed, which is vital operational knowledge.

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?

The definition is highly condensed and effective. It front-loads the constraints and use cases while maintaining a concise structure, ensuring every sentence adds instructional or clarifying value with zero unnecessary filler.

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?

The definition is complete for an orchestration layer. It defines the scope, input constraints, error handling for unknown inputs, and the operational boundary against which other sibling tools operate, leaving no significant logical gaps for the agent.

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?

Although schema coverage is 100%, the description adds critical semantic meaning that the schema lacks: the required format for product IDs ('brand:starbucks'). This informs the agent exactly how to structure the data provided in the 'ids' array.

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?

The description clearly states the tool's purpose: to compare multiple exact product IDs or brand slugs in a single call. It specifies the constraints (up to 10 IDs), making the intent unambiguous and distinct from the 'search' functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The usage guidelines are explicit and robust. It defines the boundaries of the tool (exact IDs/slug format) and provides a direct instruction for when *not* to use it, explicitly routing users toward 'search_gift_card_deals' for fuzzy discovery.

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.