Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

List reward products

list_products
Read-only

Retrieves reward products such as gift cards, PayPal, and Visa from the catalog, with filters for country, currency, category, and name search; use returned product IDs to send rewards.

Instructions

List the reward products (gift cards, PayPal, Visa, charity, ...) in the catalog. Filter by country/currency and by a name search. Use product IDs in send_rewards.products.

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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNoCase-insensitive substring of the product name
countryNoComma-separated ISO alpha-2 codes, e.g. FR,DE
categoryNoe.g. merchant_card, paypal, visa_card, charity
currencyNoComma-separated currency codes, e.g. EUR

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, so safety is covered. The description adds real context beyond that: the scope is the product catalog, results are filterable, and IDs are consumed by send_rewards. It omits pagination/limit behavior and whether results are truncated, which is a minor gap for a listing 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?

Three short sentences with zero filler: purpose first, filters second, downstream usage last. Every sentence carries information an agent needs.

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 five-parameter, optional-only listing tool with no output schema, the description covers purpose, filtering, and the downstream consumer of the IDs. It leaves the limit/pagination behavior and the category filter unaddressed, but nothing critical 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 80%, so the schema already documents search, country, category, and currency with examples. The description restates the country/currency and name-search filters without adding syntax or edge-case meaning, and never mentions the limit parameter. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ("List the reward products ... in the catalog") and enumerates the product types returned (gift cards, PayPal, Visa, charity), which lets an agent distinguish it from list_rewards. It stops short of explicitly contrasting itself with the sibling list_* tools, so it is clear but not maximally differentiated.

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 usage context: filter by country/currency and by name search, and use the returned product IDs as input to send_rewards.products. That workflow tie-in is genuinely useful. It does not state when to avoid this tool or which sibling to use instead, so it falls short of a 5.

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