Skip to main content
Glama

stake.link Agents (stakedotlink.money)

sdl_get_defi_beefy

Beefy vault metrics for stake.link related LP strategies.

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_beefy"
  }
}

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. The 'get' phrasing weakly implies a read-only lookup, but nothing is said about data freshness, caching, rate limits, auth requirements, or what happens when no Beefy vaults are linked to stake.link LP strategies.

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 eight-word sentence with no filler, and the resource is front-loaded. It is efficient, though the brevity edges toward under-specification rather than true conciseness.

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, no annotations, and no parameter documentation, the description is the only source of information, and it leaves the agent guessing what metrics are returned and in what shape. For a data-retrieval tool in a large sibling set, this is thin.

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?

The tool takes zero parameters and the input schema is an empty object, so there are no parameter semantics to explain. Per the baseline rule for 0-param tools, a 4 is appropriate; the description neither helps nor misleads here.

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?

The phrase 'Beefy vault metrics' names a specific resource (Beefy Finance vault metrics) and scopes it to 'stake.link related LP strategies', which does separate it from the other sdl_get_defi_* siblings. However, it is a bare noun phrase with no verb, so the agent must infer that it retrieves data, and it never states what 'metrics' actually comprises.

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 guidance on when to call this versus sdl_get_defi_overview, sdl_get_defi_curve, sdl_get_defi_folks, or the other protocol-specific DeFi siblings. The 'stake.link related LP strategies' scope is the only hint at selection criteria, and it is never framed as a condition.

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