Skip to main content
Glama

add_earn_rate

Add a confirmed accelerated reward rate to a card for a category, merchant, or both, so matching purchases earn the specified units per block_inr instead of the base rate.

Instructions

Add an accelerated reward rate to a card for a category, a merchant, or both. When several rates match a purchase, the most specific one wins (merchant beats category). Only add rates the user has confirmed.

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": {
      "card": "<card>",
      "rate": "<rate>"
    },
    "name": "add_earn_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYesCard id, or its name (a unique part is enough)
rateYesUnits per block_inr of the card when this rate applies (replaces the base rate, it is not added to it)
labelNoShort name, e.g. '5% on Amazon'
channelNoany
categoryNoSpending category, see the smartcard://categories resource. Leave empty to guess from a well-known merchant.
merchantNoMerchant name to match, e.g. 'Swiggy' (case-insensitive)
monthly_capNoMax units this rate can earn per statement cycle

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare this is a non-destructive write; the description adds genuinely non-obvious behavior: match precedence ('merchant beats category') and the confirmation requirement, which is a policy constraint an agent cannot infer from the schema. It stops short of saying what happens on duplicate or overlapping entries at write time.

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 short sentences: what it does, the resolution rule, then the safety constraint. Purpose is front-loaded and nothing is redundant with the schema.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. For a mutation tool the description supplies the key precedence and confirmation semantics; the only meaningful gap is behavior on conflicting or duplicate rates for the same card.

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 86%, so the baseline is 3 and the schema already explains card, rate, label, channel, category, merchant, and monthly_cap individually. The description's contribution is the relationship between category and merchant (either or both, with merchant winning), which is useful but only covers that one interaction among seven parameters.

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 and resource ('Add an accelerated reward rate to a card') plus the scoping dimension (category, merchant, or both). It is clearly distinguishable from the sibling removal tool by verb, though it does not name any sibling 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?

The closing constraint 'Only add rates the user has confirmed' gives a real precondition for invocation, and the category/merchant pairing implies when a merchant-only or category-only rate is appropriate. It never states when not to use it or points to alternatives such as remove_earn_rate or adjust_rewards for modifying existing rates.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.