get_payout_optionsAuthenticated payout options via Stripe Connect and connected user-controlled crypto wallets.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional AgentLot al_live_ key when the MCP client cannot set Authorization headers dynamically. Prefer connector-level Bearer auth for persistent integrations. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and destructiveHint already signal a safe read operation, and the description adds useful context: the results are scoped to authenticated payout options and specific provider types. It does not contradict the annotations and provides a bit extra source-level transparency.
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?
One compact sentence with no redundant wording. The most decision-relevant details—authentication and provider sources—are placed at the beginning, and every word contributes meaning.
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 read-only tool with no required parameters and a single documented optional parameter, the description is fairly adequate. But it does not clarify the shape of the returned options or how this tool relates to similarly named payout/wallet siblings, leaving a modest completeness gap.
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 single optional api_key parameter is already fully described in the input schema with 100% coverage. The description adds no paramer-level detail, so the baseline 3 applies because the schema already carries the load.
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 identifies the resource (payout options) and their two sources (Stripe Connect and connected user-controlled crypto wallets), which helps distinguish the tool from close siblings like get_payout_methods or get_wallet_providers. However, the description itself lacks an explicit verb, relying on the title's 'Get' to convey the action.
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 gives no guidance on when to choose this tool versus alternatives such as get_payout_methods, list_payment_methods, or get_wallet_providers. It only implies an authentication prerequisite, but does not state when this option should be preferred or avoided.
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.
There are multiple clusters of near-duplicate tools: earn, earn_now, earn_loop, find_money_opportunities, search_global_earn, and several rank_real_profit_opportunities variants. Even with descriptions, an agent would struggle to choose reliably among dozens of overlapping search, earn, and ranking entry points.
Most tools follow a snake_case verb_noun pattern, which provides some consistency. However, the set mixes prefixes like agentlot_, standalone verbs like earn and me, and many semantically interchangeable verbs such as find, search, discover, rank, route, and list applied to similar objects.
With 124 tools, this is an extreme mismatch for a coherent server surface. Even for a broad marketplace, this many entry points creates severe navigation overhead and includes multiple generations of similar tools instead of a disciplined, minimal API.
The tool set broadly covers marketplace lifecycles: listings, requests, orders, delivery, disputes, payouts, projects, and assets. However, there are notable gaps such as updating/unpublishing listings, canceling/refunding orders, and other core lifecycle management operations that would be expected in a complete marketplace surface.