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

lends-mcp-server

Official
by LendsProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Lends Prepare Complete Unstake

lends_prepare_complete_unstake
Read-onlyIdempotent

Build the transaction needed to complete a claimable unstake request, converting pending unstaked funds into available balance.

Instructions

Construct a transaction to complete a claimable unstake request.

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

Input Schema

NameRequiredDescriptionDefault
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that the tool constructs a transaction rather than submitting it, and that the request must be claimable. However, it does not describe behavior when the request is not claimable or what the transaction output contains.

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?

The description is a single concise sentence with no filler or repetition. It is front-loaded with the key action and resource, though adding a bit more context would improve it without sacrificing conciseness.

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

Completeness3/5

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

For a one-parameter prepare tool, the description is minimally adequate, but it does not explain where requestId comes from, what to do with the constructed transaction, or the significance of 'claimable.' Sibling tool names provide some context, but the description alone leaves gaps.

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

Parameters2/5

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

Schema description coverage is 0%, and the description never mentions requestId or how to obtain it. The only meaning comes from the parameter name and the numeric string pattern in the schema, leaving the agent to infer the request ID's source.

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 uses a specific verb and resource: 'Construct a transaction to complete a claimable unstake request.' This clearly distinguishes the tool from its request/cancel siblings, though it does not explicitly name them.

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 word 'claimable' implies the tool should be used when an unstake request is ready to be completed, but there is no explicit guidance on when to use this versus request_unstake or cancel_expired_unstake. Usage context is inferred rather than stated.

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