Skip to main content
Glama

stake.link Agents (stakedotlink.money)

sdl_get_defi_uniswap

Uniswap venue data for SDL and stake.link 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_uniswap"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 behavioral burden. It doesn't state whether this is a read operation, what permissions or auth are needed, what the return shape looks like, whether results are live or cached, or whether the SDL/stake.link filtering is inclusive. For a data-retrieval tool with zero annotation coverage this is thin.

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 no filler. It is front-loaded and easy to scan, though the lack of any scoping or output detail means it is efficient more by omission than by design.

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 annotations, no output schema, and no parameters, the description is the only source of behavioral information, and it provides almost none. For a tool whose entire value is what data it returns and how it is scoped, 'venue data for SDL and stake.link pools' leaves the agent unable to predict the response or decide when to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Parameter count is 0 and schema coverage is 100%, so there are no parameters to document and no gap to compensate for. Baseline 4 applies; the description doesn't need to add parameter semantics.

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

Purpose3/5

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

States a resource ('Uniswap venue data') and a scope (SDL and stake.link pools), which is a specific topic, but the verb/action is implicit - it doesn't say whether it returns, lists, or retrieves data. Against siblings like sdl_get_defi_curve and sdl_get_defi_morpho, which presumably follow the same 'get DeFi venue data' pattern, the topic is distinguishable but the action is not clarified.

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?

No when-to-use guidance, no when-not-to-use, no alternatives named. The sibling set includes sdl_get_defi_curve, sdl_get_defi_morpho, sdl_get_defi_beefy, and sdl_get_defi_folks, so an agent would benefit from knowing whether this is a peer of those or something different, but the description offers no routing information.

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