Skip to main content
Glama

stake.link Agents (stakedotlink.money)

sdl_build_uniswap_v3_lp

Build an unsigned mint for the canonical LINK and SDL Uniswap V3 LP NFT. This does not include NFT staking.

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_sdl": "<amount_sdl>",
      "from": "<from>"
    },
    "name": "sdl_build_uniswap_v3_lp"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesSigner wallet address.
simulateNoRun Tenderly simulation. Default: true.
recipientNoOptional LP NFT recipient.
amount_sdlYesSDL leg amount in human-readable form.
amount_linkYesLINK leg amount in human-readable form.
amount_sdl_minNoOptional minimum SDL to deploy into the position. Provide together with amount_link_min.
allow_zero_minsNoSet true to explicitly acknowledge zero minimums if you are not providing min amounts.
amount_link_minNoOptional minimum LINK to deploy into the position. Provide together with amount_sdl_min.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 behavioral load. It correctly signals the output is an unsigned transaction (not an executed mint) and scopes out staking, which is valuable. However, it omits what the agent should do with the unsigned result, whether a signer/chain context is required, and any note that simulation defaults to true.

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?

Two short sentences with zero filler; the core action is front-loaded and the scope exclusion follows immediately.

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?

For an 8-parameter transaction-building tool with no annotations and no output schema, the description is adequate but thin. It conveys the operation and one scope limit, yet leaves chain context, signing flow, and result handling unstated even though these matter for a build-and-sign tool.

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 eight parameters including the optional min-amount pairing and allow_zero_mins are already documented in structured data. The description adds no shape, format, or coupling details 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.

Purpose5/5

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

States a specific verb ('Build an unsigned mint') and resource ('canonical LINK and SDL Uniswap V3 LP NFT'), which cleanly distinguishes it from siblings like sdl_build_curve_lp_add or sdl_build_morpho_deposit. An agent knows exactly what asset and operation this concerns without opening the 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 second sentence gives one useful exclusion ('does not include NFT staking'), implicitly routing that need elsewhere, but there is no positive guidance on when to choose this build tool versus other LP or deposit tools, nor any stated prerequisites.

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