Skip to main content
Glama

Set referral payout address

set_payout_address
DestructiveIdempotent

Set the Base USDC address that receives your weekly referral payouts (null to clear). Optional to activate — get_referral_link works first; earnings accrue until an address is set. Crypto-only programme (USDC on Base). Affiliate setup only — not a purchase. Available on the full MCP server (/api/mcp). Not available on the read-only discover MCP (/api/mcp/discover).

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": {
      "payout_address": "<payout_address>"
    },
    "name": "set_payout_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
payout_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds non-obvious behavior the annotations cannot convey — that payouts are weekly USDC on Base and that earnings accrue before an address is set. It does not spell out why the write is destructive (e.g., that overwriting an address redirects all future payouts) or whether changes are recoverable, which would be the final piece of behavioral context.

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?

Front-loaded with the core action, then constrained by em-dash asides. Every clause carries information (crypto-only, optional, endpoint availability), though the trailing availability sentences make it read as a stack of caveats rather than a structured statement.

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 write tool with no output schema, this is nearly complete: it covers value semantics, clearing, side effects on earnings, asset/network, and deployment availability. The only gap is return/confirmation behavior and reversibility of an address change, which the agent must infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for the single parameter, and it does: it identifies the expected value as a Base USDC address, states what the value controls, and documents the null sentinel for clearing. That covers meaning, type semantics and clearing behavior that the bare schema (string|null) does not.

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 and resource — 'Set the Base USDC address that receives your weekly referral payouts' — with the scope clarified by '(null to clear)'. It also positions itself relative to the sibling get_referral_link, so an agent can distinguish it from the read-only referral tools without opening a schema.

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

Usage Guidelines5/5

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

Explicitly tells the agent this step is optional ('get_referral_link works first; earnings accrue until an address is set'), which is real when-to-use guidance. It also gives hard exclusions: crypto-only, affiliate setup only (not a purchase), and unavailable on the read-only discover MCP endpoint.

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