stake.link Agents (stakedotlink.money)

sdl_build_morpho_withdraw

Build an unsigned LINK withdrawal from the Morpho Alpha LINK Enhanced V2 vault.

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": {
      "amount": "<amount>",
      "from": "<from>"
    },
    "name": "sdl_build_morpho_withdraw"
  }
}

Input Schema

Name	Required	Description
`from`	Yes	Signer wallet address.
`amount`	Yes	LINK amount in human-readable form.
`receiver`	No	Optional LINK receiver.
`simulate`	No	Run Tenderly simulation. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations the description carries the full burden, and it does disclose one important trait: the transaction is 'unsigned' (build-only, not broadcast). However it is silent on the Tenderly simulation default (schema default true) and on any auth/wallet requirements, so the behavioral picture is only partially covered.

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?

A single front-loaded sentence with zero filler; the resource and vault scoping come before anything else.

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

Completeness2/5

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

For a build/mutation tool with no annotations, no output schema, and four parameters, the definition never says what 'build' actually returns (a raw unsigned tx payload?) or how the simulate flag affects the call. The description is too thin for the tool's complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents amount, from, receiver, and simulate. The description adds nothing beyond restating 'LINK amount', so the baseline 3 applies.

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 (build), resource (LINK withdrawal), and narrows it to 'the Morpho Alpha LINK Enhanced V2 vault', which cleanly separates it from the sibling sdl_build_morpho_deposit. An agent can pick this tool without opening 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 Guidelines2/5

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

There is no statement of when to use this versus siblings, no prerequisites (e.g. that the wallet must already hold a Morpho vault position), and no note on whether the result must be signed or broadcast separately. Usage is only implied by the name.

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

All stake.link Agents (stakedotlink.money) 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?