lendwise
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LENDWISE_API_URL | No | The base URL of the Lendwise API. Change to http://localhost:3000 for local development. | https://lendwise.fi |
| LENDWISE_INTEGRATION | No | Set to '1' to run network integration tests. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_market_universeA | List every asset, chain and protocol that Lendwise actually tracks, with market counts. Call this FIRST — the filter values for find_best_markets must come from here, not from memory. |
| find_best_markets | Rank current supply markets by net APY. Filtering and sorting run server-side against the latest snapshot. Defaults to markets with at least $1M TVL, because a thin market’s headline APY is mostly noise. |
| get_market_details | Full detail for one market: protocol metadata, accepted collaterals, and the current APY split into base / rewards / fees with individual reward items. |
| get_market_history | Daily net-APY history for one market plus mean / stddev / min / max. Use this before committing to a market over a long horizon: it is what separates a durable yield from a temporary reward spike. |
| optimize_allocationA | Split an amount across chosen markets to maximise yield at a target diversification, returning per-market amounts, the blended APY and a projected 6-month yield. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Both tools have distinct purposes: one lists available markets, the other optimizes allocation. There is no ambiguity between them.
Both tool names follow a consistent verb_noun snake_case pattern: list_market_universe and optimize_allocation.
Only 2 tools for a domain like yield optimization feels insufficient. The scope may be narrow, but typically more tools (e.g., for execution, historical data) would be expected.
The server lacks tools for executing allocations, retrieving market details, or managing portfolios. Significant gaps exist for practical use.