Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Cancel reward

cancel_reward
Destructive

Cancel an unredeemed, unexpired reward to refund its value, typically after a delivery failure. Use it to reverse rewards that were not delivered successfully.

Instructions

Cancel a reward and refund its value. Tremendous only allows this for rewards that are not redeemed and not expired (typically after a delivery failure).

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

Input Schema

NameRequiredDescriptionDefault
idYesReward ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered structurally. The description adds meaningful context: the refund side effect and the platform-enforced preconditions. It does not say whether the cancellation is reversible or what error surfaces when the precondition fails, leaving the failure path implicit.

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?

Two short sentences with the action and effect front-loaded, followed by the constraint. No filler, though the parenthetical could be integrated more cleanly.

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 one-parameter destructive tool with full annotation coverage and no output schema, the description covers action, side effect, and preconditions adequately. Only the post-condition and error behavior are left unstated.

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% for the single 'id' parameter, so the schema already documents it fully. The description adds no format, source, or lookup guidance for the reward ID, so baseline 3 applies.

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 ('Cancel a reward') plus a secondary effect ('refund its value'), which distinguishes it from read or resend siblings. It stops short of naming an alternative explicitly, but the action 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 clear eligibility rule — only rewards that are not redeemed and not expired — and a typical trigger ('after a delivery failure'). It does not name what to do instead when the reward is redeemed or expired, so the routing guidance is incomplete but the when-to-use condition is explicit.

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