Skip to main content
Glama
Sign In
lends-mcp-server

lends-mcp-server

Official
by LendsProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Lends Get Staking State

lends_get_staking_state
Read-onlyIdempotent

Get current sleUSD staking pool capacity, cooldown period, claimable amount, and vesting information.

Instructions

Read public sleUSD pool, capacity, cooldown, claim, and vesting state.

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": "lends_get_staking_state"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds value by specifying exactly what is read: pool, capacity, cooldown, claim, and vesting state. No contradiction with annotations.

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?

A single sentence with no filler, front-loading the verb and the resource. Every word contributes meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-argument, read-only getter, the description is complete: it names the domain (staking), the asset (sleUSD), and the specific state components returned. No output schema is present, but the listed state categories are sufficient for an agent to select and invoke the 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 input schema has zero parameters, so parameter semantics are vacuous. The baseline of 4 applies; the description correctly focuses on the output state rather than inputs.

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?

The description uses the specific verb 'Read' and names the exact resource: 'public sleUSD pool, capacity, cooldown, claim, and vesting state.' This clearly distinguishes it from sibling getters like lends_get_protocol_state or lends_get_unstake_request.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Read public...' gives clear context that this is a read-only getter for staking-related state, with no exclusions mentioned. It does not explicitly name alternatives, but the tool name and resource scope make the intended use obvious among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools