Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Send rewards

send_rewards
DestructiveIdempotent

Sends rewards by creating one Tremendous order per recipient and delivering via email, text, or link. Reuse the same draft_id on retries to prevent duplicate payments after partial failures.

Instructions

SEND rewards: this spends money and emails/texts the recipients. It cannot be undone once a reward is redeemed. Creates one Tremendous order per recipient. Prefer calling review_rewards first and let the user confirm. draft_id makes retries safe: with the same draft_id, a recipient who was already paid is not paid again (even if you remove, reorder or add other recipients), so after a partial failure retry with the same draft_id.

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": {
      "recipients": "<recipients>",
      "draft_id": "<draft_id>"
    },
    "name": "send_rewards"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNo
draft_idYesThe draft_id from review_rewards (or any unique string). Reuse it on retry.
languageNo
productsNoProduct IDs the recipient can choose from. Overrides the campaign's products.
deliver_atNoYYYY-MM-DD, within the next year. Delivered at 12pm org time.
recipientsYes
campaign_idNoTremendous campaign ID. Either campaign_id or products is required.
sender_nameNo
subject_lineNo
currency_codeNoISO 4217, e.g. EUR. Defaults to the organization currency.
delivery_methodNoEMAIL
funding_source_idNoFunding source ID, or BALANCE / INVOICE / INVOICE_THEN_BALANCE.BALANCE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructive and idempotent, but the description adds material context beyond them: money is actually spent, recipients are emailed/texted, redemption is irreversible, one order is created per recipient, and idempotency is scoped per-recipient even when the recipient list is reordered or edited. That last point is exactly the nuance annotations cannot express.

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?

Front-loaded with the cost warning, then prerequisites, then retry mechanics — the right order for a destructive tool. The draft_id explanation is slightly redundant with the schema's own draft_id description, but every sentence still carries operational value.

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?

For a 12-parameter, irreversible, payment-moving tool with no output schema, the description covers the safety profile, sequencing, and failure recovery an agent needs. It does not say what a successful call returns (order or reward identifiers) or how per-recipient failures are reported, which would help on partial-failure handling.

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 50%, and the description concentrates on draft_id, whose semantics are already documented in the schema. It adds a genuine safety guarantee about draft_id reuse across changed recipient lists, but leaves message, language, sender_name, subject_line, and the campaign_id-versus-products relationship unexplained beyond the schema.

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, front-loaded with 'SEND rewards: this spends money and emails/texts the recipients,' plus scope detail that one Tremendous order is created per recipient. It distinguishes itself from review_rewards by naming it as the prerequisite step rather than a variant of the same action.

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 a clear operating sequence: call review_rewards first and let the user confirm before sending, and retry with the same draft_id after a partial failure. It does not spell out conditions where the tool should be avoided entirely (e.g., versus generate_reward_link or cancel_reward), so it stops short of full when/when-not coverage.

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