Yield.xyz AgentKit

Enter a Yield

actions_enter

Construct unsigned transactions to stake or deposit into a yield. Does NOT execute — the user must sign each transaction exactly as returned (never modify unsignedTransaction). Amounts are human-readable strings ("1.5" = 1.5 tokens, not wei). Submit transactions in stepIndex order; for the synchronous execution pattern, wait for on-chain confirmation before submitting the next one. For ERC-4626 vaults (including RWAs like Midas), inspect yields_get → mechanics.arguments.enter.fields[] to discover yield-specific options (e.g. useMaxAllowance, receiverAddress).

Input Schema

TableJSON Schema

Name	Required	Description
`amount`	Yes	Token units e.g. "1.5" for 1.5 ETH
`address`	Yes	Wallet address that will own the position.
`yieldId`	Yes	Yield ID from yields_get_all e.g. "ethereum-eth-lido-staking".
`inputToken`	No	Deposit token address, for yields that accept more than one deposit token. Required when yields_get → mechanics.arguments.enter.fields[] lists an inputToken field with required: true; that field's options[] holds the valid addresses, which also appear as yields_get → inputTokens[].address. Use "0x" to deposit the network's native token.
`executionMode`	No	Transaction execution mode. Defaults to "individual". "batched" is reserved for future use — batch mode is not yet available across all yields and should not be used until fully enabled.
`receiverAddress`	No	Optional. ERC-4626 vault convenience field. Address that should receive the minted vault shares. Defaults to the position owner (`address`). Honored only when listed in yields_get enter schema.
`useMaxAllowance`	No	Optional. ERC-4626 vault convenience flag. true = approve the maximum (uint256 max) allowance, so subsequent deposits skip a fresh APPROVAL step. false = approve only the exact amount being deposited. Honored only when listed in yields_get enter schema.
`validatorAddress`	No	Validator to delegate to. Required when yields_get returns mechanics.requiresValidatorSelection=true.
`inputTokenNetwork`	No	Network of the input token e.g. "ethereum". Only for cross-chain deposits, where the deposit token is not on the vault's own network.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`type`	Yes
`amount`	Yes
`intent`	Yes
`status`	Yes
`address`	Yes
`yieldId`	Yes
`amountRaw`	Yes
`amountUsd`	Yes
`createdAt`	Yes
`completedAt`	Yes
`rawArguments`	Yes
`transactions`	Yes
`executionPattern`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, but the description goes well beyond: it discloses that transactions are unsigned, must never be modified, amounts are human-readable strings (not wei), and must be submitted in stepIndex order with confirmation waits. That is exactly the behavioral context annotations can't convey.

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?

Four dense sentences with no filler; the critical non-execution constraint is front-loaded. Slightly dense but every clause (signing, ordering, ERC-4626 discovery) carries actionable weight.

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?

With an output schema present and annotations covering the safety profile, the description fills the remaining gaps: signing workflow, ordering constraints, confirmation-waiting, and the sibling discovery call for yield-specific options. Nothing an agent needs to invoke correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description additionally reinforces amount semantics ('1.5' = 1.5 tokens, not wei) and points to yields_get mechanics.arguments.enter.fields[] for discovering yield-specific options like useMaxAllowance/receiverAddress, adding real value over schema alone.

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?

Opens with a specific verb+resource: 'Construct unsigned transactions to stake or deposit into a yield.' This is clearly distinguishable from the sibling actions_exit (which withdraws) without needing to open any schema.

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?

Explicitly states this tool does NOT execute and that the user must sign each transaction unmodified, plus ordering (stepIndex) and confirmation-waiting guidance. It lacks an explicit 'use actions_exit instead when...' routing, but the usage context is otherwise strong.

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

All Yield.xyz AgentKit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?