stake.link Agents (stakedotlink.money)

sdl_build_stake_link

Build an unsigned LINK to stLINK transaction through the stake.link Priority Pool.

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_stake_link"
  }
}

Input Schema

Name	Required	Description
`from`	Yes	Signer wallet address.
`amount`	Yes	LINK amount in human-readable form.
`simulate`	No	Run Tenderly simulation. Default: true.
`shouldQueue`	No	Queue the deposit if instant capacity is unavailable. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 2026

TDQS

A3.7/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 behavioral burden, and it does disclose the key trait 'unsigned' (i.e., it constructs but does not broadcast or mutate state). It does not explain what the agent must do with the result (sign/submit), nor the implications of the simulate/queue defaults, so meaningful gaps remain for a transaction-building tool.

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 naming the action, direction, and execution venue with zero filler. Nothing could be removed without losing information.

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

Completeness3/5

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

There is no output schema and no annotations, so the description should ideally describe the returned unsigned transaction and any prerequisites for signing. It partially covers this by saying the built transaction is 'unsigned' and scoped to the Priority Pool, but leaves the return payload and follow-up steps unstated.

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% across all four parameters, so the schema already documents 'from', 'amount', 'simulate', and 'shouldQueue'. The description adds no parameter-level detail beyond what the schema provides, making the baseline 3 correct.

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'), the exact resource ('unsigned LINK to stLINK transaction'), and the venue ('stake.link Priority Pool'). The directional LINK→stLINK phrasing cleanly separates it from siblings like sdl_build_unstake_link and sdl_build_wrap_stlink without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage (deposit LINK into the Priority Pool to receive stLINK) and the venue narrows the choice among the many sdl_build_* siblings. However it never states when to prefer this over sdl_build_wrap_stlink or what to do when capacity is unavailable, so guidance is only implied, not explicit.

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?