Skip to main content
Glama

stake.link Agents (stakedotlink.money)

sdl_get_defi_curve

Curve venue data for stLINK and wstPOL pools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sdl_get_defi_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoCurve deployment. Default ethereum.

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?

No annotations are provided, so the description carries the full burden. It implies a read operation, but says nothing about what the returned data contains, whether it requires auth, or its freshness/caching behavior. For a data-fetch tool with zero structured coverage this is a notable gap.

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 short sentence with the resource front-loaded and zero filler. It is arguably too terse for the information it should convey, but from a pure conciseness standpoint it wastes nothing.

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?

With no output schema and no annotations, the description should compensate by describing what the returned venue data includes (liquidity, APY, balances), yet it does not. For a data-retrieval tool the agent is left guessing at the payload, making this incomplete.

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 the single chain parameter and its 'Default ethereum' semantics are already fully documented in the schema. The description adds no additional meaning about the parameter, 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 resource (Curve venue data) scoped to two concrete pools (stLINK and wstPOL), which lets an agent distinguish it from sibling venue tools like sdl_get_defi_uniswap and sdl_get_defi_morpho without opening a schema. However, 'venue data' is generic and doesn't state what metrics are actually returned, so it stops short of a fully precise purpose statement.

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 explicit routing versus the numerous sibling sdl_get_defi_* tools. The pool names hint at scope but the agent is left to infer that this is the Curve-specific fetch tool.

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