Skip to main content
Glama

Finance App Radar referral codes

Find a verified referral code

find_referral_code
Read-only

Returns the verified referral code or referral link for one app (e.g. 'Underdog', 'Kling AI', 'Novig', 'Courtside', 'Muse'), with the exact field and moment to enter it, the sign-up destination and whether it carries the referral, the new user benefit, the steps, the conditions, and the verification date.

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": {
      "app": "<app>"
    },
    "name": "find_referral_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesApp or company name, e.g. 'Underdog Fantasy' or 'Kling'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by enumerating what comes back (exact field and moment to enter it, sign-up destination, benefit, steps, conditions, verification date), which stands in for a missing output schema. It omits the miss case — what is returned or whether anything fails when no verified code exists for an app.

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?

It is a single front-loaded sentence that states the core return first, then the payload details. The trailing comma-separated enumeration is slightly run-on but each item describes a distinct returned field, so the content earns its place.

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, annotated, read-only lookup with no output schema, enumerating the returned fields is exactly the right compensation. The remaining gap is the not-found / no-verified-code path, which an agent would want to know before calling on an ambiguous app name.

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% for the single 'app' parameter, and the schema already supplies examples ('Underdog Fantasy', 'Kling'). The description's example list largely duplicates that, though it adds breadth (Novig, Courtside, Muse) and signals that app aliases are acceptable. Baseline 3 is appropriate since the schema carries the parameter documentation.

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 uses a specific verb ('Returns') and resource ('the verified referral code or referral link') scoped precisely to 'one app', with concrete examples (Underdog, Kling AI, Novig). The singular-per-app scope implicitly separates it from the sibling list_referral_offers, but the sibling is never named, so differentiation is inferred rather than stated.

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?

Usage is only implied: an agent can infer this is for looking up a code when it already knows the app name, versus browsing offers. There is no explicit when-to-use, when-not-to-use, or named alternative guidance, and no mention of prerequisites or what to do when the app is unknown.

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