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

lends-mcp-server

Official
by LendsProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Lends Get Unstake Request

lends_get_unstake_request
Read-onlyIdempotent

Retrieve a sleUSD unstake request by its unsigned request ID to view its details.

Instructions

Read one sleUSD unstake request by unsigned request ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "requestId": "<requestId>"
    },
    "name": "lends_get_unstake_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the description's main job is to add request-specific context. It adds 'one' and 'unsigned request ID' but does not describe return value, not-found behavior, or how the ID relates to other tools. This is adequate but not rich.

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?

One short sentence, front-loaded with the action and resource, no filler. Every word contributes meaning.

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

Completeness4/5

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

For a single-parameter read tool with strong safety annotations, 'Read one ... by unsigned request ID' conveys the essential call shape and purpose. It is less complete than it could be because there is no output schema and no description of the returned request data, but the low complexity keeps the gap small.

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?

With 0% schema description coverage, the description must explain the parameter, and it does identify the requestId semantically as an 'unsigned request ID,' matching the non-negative integer pattern. However, it does not clarify where the ID comes from or distinguish 'unsigned' from 'signed' request contexts, leaving some ambiguity.

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 specifies a concrete action ('Read one ... request') and a precise resource ('sleUSD unstake request'), with the qualifier 'unsigned request ID.' It is more specific than the tool name alone and clearly separates this read operation from the prepare_* and math siblings.

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

Usage Guidelines3/5

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

The verb 'Read' implies the tool is for inspecting a single unstake request, but the description does not state when to prefer it over alternatives such as prepare_complete_unstake or prepare_cancel_expired_unstake. No explicit when/when-not guidance is provided.

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