Skip to main content
Glama

Finance App Radar referral codes

List referral offers

list_referral_offers
Read-only

Lists every active referral offer (app, code, sign-up link, what the new user gets, verification date), optionally filtered by category: 'ai', 'sports', 'money' or 'all'.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds meaningful context beyond them: only *active* offers are returned, and the fields each offer exposes are enumerated, effectively standing in for the absent output schema. Pagination or ordering behavior is not mentioned.

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 resource, with the optional filter clause placed after the core information. No wasted wording.

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 single-optional-parameter read-only list tool, the description covers scope (active only) and return fields, which is most of what an agent needs. Minor omissions like result ordering or volume are unlikely to block correct invocation.

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 100% and the enum values ('all', 'ai', 'sports', 'money') are already declared in the schema, so the description largely restates structured data. It adds only the framing that the parameter is an optional category filter, without explaining what aspect of the offer the category describes.

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?

States a specific verb (Lists) and resource (active referral offers), and enumerates what each offer contains (app, code, sign-up link, reward, verification date), which also distinguishes it from a lookup-style sibling like find_referral_code.

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

Usage Guidelines3/5

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

'Optionally filtered by category' implies the main usage pattern, but there is no explicit guidance on when to use this list versus the sibling find_referral_code, nor any prerequisites or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources