MCP server for JustLend V1 DAO on TRON blockchain. Supports supply, borrow, repay, withdraw, market data, mining rewards (USDD/WBTC), API integration, general TRON chain utilities, and AI-guided DeFi prompts.
Scoring was not performed
Output schemas not documented. Tool definitions show input schemas but do NOT specify what fields are returned. LLMs cannot plan downstream tool calls or extract required data without knowing response structure.
Descriptions are uniformly short (30-80 chars) and lack context on WHEN to use each tool. No guidance on prerequisites, dependencies, or how to choose between similar tools (e.g., get_trx_balance vs get_account_trx_balance are near-duplicates with unclear distinction).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 30 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 36 | - | v1 |
Parameter descriptions are minimal or absent. For example, 'address' params lack format guidance (Base58 vs hex expected?). 'network' param description is generic; no guidance on valid values beyond 'mainnet or nile'.
No error handling strategy documented in tool definitions. What happens if an address is invalid? If a network is unsupported? If an RPC call times out? No guidance for LLM recovery.
Duplicate or near-duplicate tool names create ambiguity. 'get_account_trx_balance' vs 'get_trx_balance' and 'get_account_data_from_api' vs 'get_account_summary' overlap in purpose. LLM will struggle choosing between them.
No pagination or result limiting documented for tools that could return large result sets (e.g., get_account_summary may return data across multiple markets). No limit, page, or cursor parameters visible.
No mention of idempotence or retryability in descriptions. Agents need to know which tools are safe to retry (all read-only tools here are, but this is not explicit).