Skip to main content
Glama

stake.link Agents (stakedotlink.money)

sdl_get_defi_folks

Folks Finance venue data for wstLINK.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 entire behavioral burden. It discloses nothing about whether this is a read, whether auth is needed, what 'venue data' contains, or the response shape. For a zero-annotation tool the description should at least confirm it is a safe read and sketch what is returned; it does neither.

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 phrase with no filler, and the distinguishing token (Folks Finance) is front-loaded. It is appropriately terse for a no-argument tool, though the extreme brevity leans toward under-specification rather than crispness.

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 parameter schema, and no output schema, the description is the only source of information and it is one sentence. It never explains what 'venue data' includes (TVL, rates, positions?) or what the agent should expect back, leaving a real gap for a data-retrieval tool.

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, so there is no parameter semantics to explain and nothing for the description to compensate for. Baseline for a 0-param tool is 4.

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 — 'Folks Finance venue data' — scoped to 'wstLINK', which clearly separates it from sibling venue tools like sdl_get_defi_curve, sdl_get_defi_morpho, and sdl_get_defi_beefy. It omits an explicit verb, but the 'data for X' phrasing makes the intent ('retrieve this venue's data') recoverable. Clear enough to distinguish, slightly weaker than a full verb+resource 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 condition that selects this over the other sdl_get_defi_* venue tools, and no mention of prerequisites. The reader must infer from the name that this is the Folks Finance slice of the DeFi data family. No explicit alternatives or exclusions are offered.

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