stake.link Agents (stakedotlink.money)

sdl_strategy_plan

Deterministic public strategy planner. Builds ordered steps, warnings, live checks, and step output references for one supported route.

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": {
      "strategy_id": "<strategy_id>"
    },
    "name": "sdl_strategy_plan"
  }
}

Input Schema

Name	Required	Description
`wallet`	No	Optional wallet address for pre-filled builder calls.
`amount_sdl`	No	Optional SDL amount to thread into the Uniswap V3 strategy plan.
`amount_link`	No	Optional LINK amount to thread into the plan.
`strategy_id`	Yes	Which public strategy to plan.
`slippage_bps`	No	Optional slippage guard for swap and LP steps. Default: 50.
`amount_sdl_min`	No	Optional SDL minimum for the Uniswap LP builder step.
`allow_zero_mins`	No	Optional explicit acknowledgement for zero-minimum Uniswap LP minting. Only use this when you intentionally accept that risk.
`amount_link_min`	No	Optional LINK minimum for the Uniswap LP builder step.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 2026

TDQS

B3.2/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. It usefully discloses that the tool is deterministic, performs 'live checks', and emits warnings and step output references, but it never states whether it is read-only or executes on-chain actions — a critical distinction among the sdl_build_* siblings — and gives no auth or permission notes.

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?

Two tight sentences with the core role front-loaded and zero filler. Slightly terse given the complexity it could have clarified, but efficient.

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?

With no output schema, the description does partially cover return values (ordered steps, warnings, live checks, output references), and all eight params are schema-documented. However, it omits whether the planner mutates state or the expected workflow with sdl_strategies_list and sdl_build_*, leaving a meaningful gap for a tool in this family.

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 every parameter is already documented in the schema and the baseline is 3. The description adds only the notion of 'one supported route', which loosely maps to the strategy_id enum but adds no format or syntax detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('Deterministic public strategy planner') and enumerates its outputs (ordered steps, warnings, live checks, output references), which distinguishes it from the sdl_build_* executors that actually construct transactions. It stops short of explicitly naming the sibling it is not, so it earns a 4 rather than 5.

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 when-to-use guidance or routing to alternatives. Given the crowded sibling set (sdl_strategies_list for discovery, sdl_build_* for execution), the description never tells the agent when to plan versus when to build or list.

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?