Skip to main content
Glama
justlend

mcp-server-justlend

Official
by justlend

moolah_repay

Destructive

Repay a Moolah market loan on JustLend. Use 'max' for full repayment; for TRC20, approve proxy first, TRX sent directly.

Instructions

Repay a Moolah market loan. Use amount='max' to repay the full outstanding borrow (uses shares math for exact settlement). For TRC20 loan tokens, call approve_moolah_proxy first. For TRX loans, TRX is sent directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesLoan amount to repay, or 'max' for full repayment
networkNoNetwork. Default: mainnet
marketIdYesMarket ID (bytes32 hex)
Behavior4/5

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

Description adds behavior beyond annotations: mentions 'shares math for exact settlement' and token-specific prerequisites. Annotations already indicate destructiveHint=true, but description provides helpful context without contradiction.

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?

Three focused sentences covering purpose, special value, and token-specific details. No wasted words, front-loaded with the primary action.

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?

Adequately complete for the tool's complexity: covers basic operation, special values, and token-specific steps. Lacks details on return value or transaction confirmation, but acceptable given typical patterns.

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?

Schema covers all parameters (100% coverage). Description adds value by explaining 'max' usage and prerequisite workflow for TRC20 tokens, augmenting the schema's type/pattern constraints.

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?

Description clearly states 'Repay a Moolah market loan' with specific verb and resource. It distinguishes from similar tools like 'moolah_borrow' and 'supply', but does not explicitly differentiate from the generic 'repay' sibling, which slightly reduces clarity.

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?

Provides clear instructions: use 'max' for full repayment, and prerequisites for TRC20 vs TRX loans. Does not mention when not to use or alternatives, but the context is sufficient for correct usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/justlend/mcp-server-justlend'

If you have feedback or need assistance with the MCP directory API, please join our Discord server