Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Resend reward

resend_reward
Destructive

Resend a reward email or SMS after a failed delivery, optionally correcting the recipient email or phone to resolve the delivery issue.

Instructions

Resend a reward email/SMS. Tremendous only allows this after a delivery failure (delivery_status FAILED). Optionally correct the email (EMAIL rewards) or the phone (PHONE rewards), not both.

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

Input Schema

NameRequiredDescriptionDefault
idYesReward ID
updated_emailNoSend to this corrected email instead
updated_phoneNoSend to this corrected phone instead

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description adds real value by explaining the server-side gating rule (delivery failure required) that an agent cannot see in the schema. It stops short of saying what error occurs if the precondition is unmet or whether the original reward record/link is replaced.

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, front-loaded with the action and followed by the gating condition and the parameter constraint. Every clause carries information; nothing is repeated from 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?

For a three-parameter mutation tool with full schema coverage and annotations, the description supplies the crucial business rule and the parameter exclusivity rule. Only failure behavior (what happens if the reward was not FAILED, or if both correction fields are supplied) is left unspecified.

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 100% and each parameter is already documented, so the baseline is 3. The description does add meaning beyond the schema by tying updated_email to EMAIL rewards and updated_phone to PHONE rewards and declaring them mutually exclusive.

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 ('Resend a reward email/SMS') and immediately qualifies the scope with the delivery-failure precondition. It does not explicitly name a sibling such as send_rewards to contrast with, so it falls short of a 5, but the purpose is unambiguous.

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 hard precondition (only permitted when delivery_status is FAILED), which is exactly the kind of when-to-use gate an agent needs. It does not name the alternative tool for first-time or non-failed sends, so it stops short of full routing guidance.

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