Skip to main content
Glama

stake.link Agents (stakedotlink.money)

sdl_build_curve_swap

Build an unsigned swap in the canonical Curve stLINK and LINK 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_in": "<amount_in>",
      "from": "<from>"
    },
    "name": "sdl_build_curve_swap"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesSigner wallet address.
simulateNoRun Tenderly simulation. Default: true.
amount_inYesInput amount in human-readable form.
directionNoSwap direction. Default: link_to_stlink.
slippage_bpsNoSlippage guard in basis points. Default: 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden, but it does disclose the key trait that the output is 'unsigned' (i.e. not broadcast, requires separate signing). It omits other behavioral context such as simulation behavior, whether approvals are needed, or how the unsigned payload should be handled downstream.

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 zero filler; the action and target resource come first. It is appropriately short, though the very brevity leaves little structure to hang additional guidance on.

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 annotations and no output schema, the description should carry more of the workflow burden for a DeFi transaction builder. It covers the core action and notes the result is unsigned, but says nothing about the signing/submission step the agent must perform afterward.

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 (from, simulate, amount_in, direction, slippage_bps) is already documented in the schema with defaults and enums. The description adds no additional parameter meaning, so the baseline of 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?

States a specific verb ('Build') and resource ('unsigned swap in the canonical Curve stLINK and LINK pool'), which cleanly separates it from sibling builders like sdl_build_curve_lp_add or sdl_build_uniswap_v3_lp. It does not explicitly name alternatives, but the pool-specific scope makes the target 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 when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as a direct swap execution tool. The agent must infer usage entirely from the 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