Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Get reward

get_reward
Read-only

Retrieve a specific reward by ID to view its recipient, value, delivery method, and delivery status.

Instructions

Get one reward: recipient, value, delivery method and delivery status.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-lookup behavior are covered without the description's help. The description does add the returned fields (recipient, value, delivery method, delivery status), which is genuinely useful because no output schema exists. It says nothing about what happens for an unknown id or about rate limits, so the addition is modest.

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?

One sentence, front-loaded with the verb and scope, with every clause earning its place by enumerating the returned payload. There is no filler, hedging, or redundancy.

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?

For a simple single-record read with annotations covering the safety profile and no output schema, listing the returned fields is a reasonable completeness gesture. However, the sole input parameter is undocumented and there is no guidance on failure or empty results, leaving real gaps for an agent that must supply a correct id.

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 0% – the single 'id' parameter is a bare string with no format, source, or example documented anywhere. The description's 'one reward' weakly implies the id identifies a reward, but it does not state whether it is the reward id versus an order or campaign id, nor give a format. The schema does none of the work here, so a 3 reflects partial but insufficient compensation.

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 gives a specific verb ('Get') and resource ('reward') and scopes it to a single record ('one reward'), which implicitly separates it from list_rewards and the other list_* siblings. It does not name an alternative explicitly, but the resource is distinct enough that an agent won't confuse it with get_account, get_campaign, or get_order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says you need a known reward id, nothing excludes list_rewards or review_rewards as the path for browsing rewards, and no prerequisites (auth scope, permissions) are mentioned. The single-record framing hints at the use case but leaves the agent to infer it.

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