Create a payout recipient
Creates a person or company money can be sent to. Bank details are attached separately with addBankingDestination.
Free.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The recipient's name. | |
| address | No | The recipient's postal address. Required before a bank destination can be attached, so supplying it here avoids a second call. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / auth_tokenRemoved value: -{
- "description": "Laso credential. Only if the MCP connection has no Authorization header.",
- "type": "string"
-}Output schema / (root)Previous value: -nullNew value: +{
+ "type": "object"
+}Output schema / (root)Previous value: -{
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false (write operation) and idempotentHint=false. The description adds 'Free' (a cost signal) but otherwise does not disclose potential failures, side effects, or prerequisites beyond what the schema provides. Since annotations cover the basic safety profile, this is adequate but not exceptional.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured: a title, a one-sentence definition, a key usage note pointing to the next step, and a cost indicator. No redundant information, and all sentences earn their place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple create operation with two parameters and a rich schema (100% coverage) and an output schema present, the description is sufficiently complete. It covers the main purpose, the next step (addBankingDestination), and a key prerequisite (address). It doesn't explain return values but the output schema presumably does.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers both parameters, and the description adds meaningful context: it explains that address is required before a bank destination can be attached, and supplying it here avoids a second call. This enhances understanding of the address parameter beyond the schema's basic description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool creates a payout recipient (a person or company) and differentiates it from attaching bank details by referencing addBankingDestination. This distinguishes it from sibling tools like add_banking_destination and delete_banking_recipient, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context that bank details are attached separately via addBankingDestination, implying the correct sequence of use. However, it does not explicitly mention when not to use this tool or alternatives like update_payment_recipient, so it is slightly incomplete but still helpful.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.