Affilync MCP Server

requestPayout

Destructive

Request a payout of your available affiliate earnings. Omit the amount to withdraw your full balance.

Instructions

Request a payout of your available earnings. IRREVERSIBLE — moves real money. Omitting the amount requests your full available balance.

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": "requestPayout"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	No	Amount to request (defaults to full available balance)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description explicitly states the tool is irreversible and moves real money, which aligns with the destructiveHint: true annotation and adds valuable behavioral context beyond what annotations alone provide.

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?

Two concise sentences: first states purpose, second provides critical warning and parameter behavior. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter, no output schema, and annotations covering safety profile, the description is complete. It covers purpose, side effects, and parameter behavior adequately.

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

Parameters4/5

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

The single parameter 'amount' is fully described in the schema, and the description adds clarity about default behavior (full balance) that is not in the schema's description field. Schema coverage is 100%, so baseline is 3; the additional context raises it to 4.

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?

The description clearly states 'Request a payout of your available earnings,' using a specific verb and resource. No sibling tool overlaps, making it distinct.

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?

The description provides clear context (irreversible, moves real money) and explains default behavior when amount is omitted. However, it does not explicitly state when to use this tool over alternatives, though no direct alternatives exist among siblings.

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