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

lends-mcp-server

Official
by LendsProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Lends Prepare Approve

lends_prepare_approve
Read-onlyIdempotent

Constructs an exact ERC-20 approval transaction; setting amount to 0 revokes approval.

Instructions

Construct an exact ERC-20 approval transaction; amount 0 revokes approval.

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": {
      "token": "<token>",
      "spender": "<spender>",
      "amount": "<amount>"
    },
    "name": "lends_prepare_approve"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
amountYes
spenderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to re-establish safety. It adds valuable behavioral context beyond annotations by noting the transaction is 'exact' and that amount 0 revokes approval. This is useful ERC-20-specific behavior not captured in the schema or 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?

The description is a single well-structured sentence that leads with the core action and then adds the critical amount-0 caveat. Every word earns its place, with no filler or repetition of the title.

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 straightforward three-parameter tool with safety annotations, the description covers the core behavior and the amount edge case. It is incomplete, however, because it never explains how this generic tool relates to the multiple specialized approve siblings, which is essential for correct tool selection in this context.

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%, so the description bears the burden of explaining token, spender, and amount. It only explains the amount-0 revocation behavior and does not clarify the meaning or relationship of token and spender beyond their self-evident names. This is only partial compensation for the missing schema descriptions.

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 clearly states the tool constructs an ERC-20 approval transaction, with a specific verb ('construct') and resource ('ERC-20 approval transaction'). It also adds the key semantic that amount 0 revokes approval. However, it does not distinguish this generic approve tool from the many specialized sibling tools like lends_prepare_approve_collateral or lends_prepare_approve_leusd_for_repay.

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 about when to use this generic approval transaction builder versus the specialized approve siblings. The description does not mention that specialized variants exist or that this tool should be used only for arbitrary token/spender pairs. An agent is left to infer usage from the bare parameter names.

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