Skip to main content
Glama

Add a reward to a card

create_reward

Adds a reward that customers can redeem with stamps from a card, e.g. a free coffee at 10 stamps.

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_id": "<card_id>",
      "name": "<name>",
      "stamps_required": "<stamps_required>"
    },
    "name": "create_reward"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWhat the customer gets, e.g. "Free coffee".
intentNoOptional. One short sentence on what the person asked you to do, e.g. "Set up a stamp card for Ground Up Café". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.
card_idYesCard id from list_cards.
descriptionNoOptional details, e.g. "Any size, any drink".
stamps_requiredYesStamps spent to redeem it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / intent
      Added value: +{
      +  "description": "Optional. One short sentence on what the person asked you to do, e.g. \"Set up a stamp card for Ground Up Café\". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation profile is covered. The description adds useful domain meaning (a reward is a redemption tier tied to a stamp count) but says nothing about error cases, whether the reward is immediately live, or what limiting factors apply.

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?

A single front-loaded sentence with the core action first and a clarifying example second. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers what is created and where, but for a create tool with no output schema it leaves gaps: what is returned (a reward id?), whether stamps_required must relate to the card's existing threshold, and what happens on duplicate or invalid input. Adequate but not complete.

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%, so parameter documentation is already handled by the schema, and the scoring baseline is 3. The example "free coffee at 10 stamps" loosely illustrates name and stamps_required but adds no constraints or semantics beyond what the schema states.

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 verb and resource ("adds a reward") and explains the domain concept with a concrete example ("a free coffee at 10 stamps"). It does not explicitly distinguish itself from siblings like update_reward or create_card, so it falls short of a 5.

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?

Usage is only implied: the phrase "from a card" suggests the card must already exist, and the schema's card_id note points at list_cards. There is no explicit when-to-use or when-not guidance, and no mention of update_reward for changing an existing reward.

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