Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Generate reward link

generate_reward_link
Destructive

Create a redemption link for a LINK-delivery reward so a recipient can redeem it; share the link only with the intended recipient.

Instructions

Create a new redemption link for a LINK-delivery reward (other rewards return 403). WARNING: anyone with this link can redeem the reward. Share it only with the recipient.

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

Input Schema

NameRequiredDescriptionDefault
idYesReward ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and openWorldHint=true; the description adds real value by explaining why the operation is consequential (anyone holding the link can redeem) and by disclosing the 403 failure mode. It says nothing about permissions/authorization needed to mint a link, or whether repeated calls create multiple independent links, which matters for a destructive-flagged creation tool.

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?

Two sentences, zero waste, with the scope constraint and the security warning both front-loaded before any invocation detail. Nothing is padded or repeated from the title.

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 creation tool with no output schema, the description covers the eligibility rule and the key risk. It is slightly thin on what the returned link looks like and on auth requirements, but nothing essential to correct invocation is missing.

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 the single `id` param is already documented as "Reward ID," so the schema does the heavy lifting. The description does add one constraint on that id — it must reference a LINK-delivery reward — but gives no format or lookup guidance.

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?

The description opens with a specific verb and resource ("Create a new redemption link") and immediately narrows scope to "a LINK-delivery reward," which cleanly separates it from siblings like send_rewards or resend_reward. The parenthetical 403 clause further pins down the exact case it covers.

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?

It states a clear precondition and an explicit exclusion: only LINK-delivery rewards work, others return 403. It does not name a sibling to use instead for non-LINK rewards, so the agent knows when not to call this but not where to redirect.

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