Skip to main content
Glama

arena_referrals

Read-only

FREE: list bots referred by a payout wallet, their 3-day pulse+predict progress, and referral earnings (base $0.005 / bonus $0.01 USDC). Same data as GET /v1/arena/referrals?wallet=.

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": {
      "wallet": "<wallet>"
    },
    "name": "arena_referrals"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesReferrer's payout wallet (Solana base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 safety is covered. The description adds useful context beyond that: the call is free, the earnings rates (base $0.005 / bonus $0.01 USDC), and the REST equivalent GET /v1/arena/referrals?wallet=. It says nothing about result size, pagination, or behavior for a wallet with no referrals.

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?

One sentence, front-loaded with the cost signal and then the resource and contents. Dense but every clause carries information; the trailing REST-endpoint mapping is the only marginally expendable part.

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 read tool with no output schema, the description conveys what comes back (referred bots, progress, earnings) and that it is free. That is enough for an agent to call it correctly, with only empty-result behavior left unstated.

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 100% and the single parameter already documents itself as the referrer's Solana base58 payout wallet. The description only restates 'payout wallet', adding no format, validation, or edge-case meaning beyond the schema.

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?

Names a specific verb (list) and precise resource (bots referred by a payout wallet), plus the payload contents (3-day pulse+predict progress, referral earnings). It is clearly not the leaderboard, history, or results tools, though it never names a sibling explicitly.

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?

The 'FREE:' prefix implies this is the zero-cost way to get referral data, but there is no explicit when-to-use vs. when-not guidance and no stated prerequisites or alternatives. Usage is inferred from the resource name alone.

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