Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Who received rewards

list_rewards
Read-only

Find which recipients received rewards by filtering by email, name, date range, campaign, or delivery status; returns per-recipient totals and reward rows with offset pagination for truncated results.

Instructions

Find which people received rewards. Filter by recipient email or name (substring), date range, campaign and delivery status. Returns one summary per recipient (count and total) and the reward rows, and shows an interactive table. Tremendous cannot filter by recipient, so this scans up to max_scan rewards (newest first); if truncated is true, call again with offset=next_offset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_rewards"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailNo
sinceNoISO 8601 date or datetime, inclusive
untilNoISO 8601 date or datetime, inclusive
offsetNo
max_scanNo
campaign_idNo
delivery_statusNo

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 readOnlyHint=true and openWorldHint=true, and the description still adds real value beyond them: a scan cap (max_scan, newest-first ordering), a truncation/next_offset pagination contract, and the fact that results include both aggregates and raw rows plus an interactive table. It does not discuss ordering guarantees beyond 'newest first' or performance costs of large scans, which keeps it from a 5.

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?

Three dense sentences, front-loaded with purpose, then filters, then return shape and pagination fallback — no filler. The final sentence is compressed and requires careful reading, but every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and 8 optional parameters, the description supplies what is otherwise missing: the shape of the return (per-recipient count and total plus reward rows), the presence of an interactive table, and the truncation/offset loop for getting complete results. An agent can call this repeatedly until done without guessing at undocumented behavior.

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 only 25%, so the description carries real weight, and it does compensate for most parameters by explaining substring matching on name/email, the date range, campaign and delivery-status filters, and the max_scan/offset pagination pair. However, several parameters (campaign_id format, the offset default relationship to next_offset, the meaning of max_scan defaults) are only gestured at rather than explained, so it is slightly above baseline rather than fully compensatory.

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?

Opens with a specific verb+resource framing ('Find which people received rewards') and then enumerates filter dimensions and the return shape (per-recipient summary plus reward rows). It is clearly distinguishable from get_reward (single reward) and review_rewards (reviewing), though it never explicitly names a sibling to contrast with.

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 concrete operational context: filtering is done client-side because 'Tremendous cannot filter by recipient', so it scans newest-first up to max_scan, and tells the agent to re-call with offset=next_offset when truncated is true. That is strong guidance for a paginated scan, but there is no explicit statement of when to prefer this over sibling tools such as review_rewards or list_orders.

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