Skip to main content
Glama

stake.link Agents (stakedotlink.money)

sdl_build_curve_lp_add

Build an unsigned balanced Curve LP add transaction for LINK and stLINK.

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_link": "<amount_link>",
      "amount_stlink": "<amount_stlink>",
      "from": "<from>"
    },
    "name": "sdl_build_curve_lp_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesSigner wallet address.
simulateNoRun Tenderly simulation. Default: true.
amount_linkYesLINK leg amount in human-readable form.
slippage_bpsNoSlippage guard in basis points. Default: 50.
amount_stlinkYesstLINK leg amount in human-readable form.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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 does disclose that the output is unsigned and that the add is balanced, which is useful, but it says nothing about simulation defaults, slippage guards, or the fact that the result must be signed externally.

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?

A single front-loaded sentence with no wasted words. It is efficient, though its brevity is partly a consequence of under-specification rather than disciplined editing.

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 5-parameter transaction-building tool with no annotations and no output schema, the description is thin. It never clarifies what the agent gets back (unsigned calldata?) or the simulate/slippage behavior, leaving key call-time context missing.

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 all five parameters are already documented. The description only implies the LINK/stLINK leg mapping and the 'balanced' constraint, adding little beyond the schema, so the baseline 3 applies.

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 names a specific verb (Build), resource (unsigned balanced Curve LP add transaction), and the two constituent tokens (LINK, stLINK), which clearly separates it from siblings like sdl_build_curve_swap and sdl_build_curve_gauge_deposit. It stops short of explicitly contrasting those siblings, but the resource is unambiguous.

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 tool versus alternatives such as the Curve gauge deposit or Uniswap V3 LP builders, and no prerequisites are given. Usage must be inferred entirely from the tool name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources