NEAR DeFi Dashboard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_defi_yieldsA | Get current APY/APR yields across all major NEAR DeFi protocols (Ref Finance, Burrow, Meta Pool, Linear) |
| compare_staking_optionsB | Compare native staking vs liquid staking (stNEAR, LiNEAR) vs DeFi yields for a given NEAR amount |
| find_best_swap_routeA | Find the optimal swap route on Ref Finance for token exchange |
| get_lending_ratesA | Get current borrow and supply rates on Burrow lending protocol |
| calculate_impermanent_lossA | Calculate impermanent loss for liquidity provider positions |
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 5 tools
Each tool targets a distinct DeFi operation (yields, staking comparison, swaps, lending rates, IL). However, get_defi_yields and get_lending_rates both return yield-type information, which could cause minor confusion.
The naming follows a consistent get_/compare_/find_/calculate_ verb pattern, mostly noun_phrases with clear intent. The slight mix of 'get' vs 'compare/find/calculate' is minor and still predictable.
5 tools is well-scoped for a NEAR DeFi dashboard covering yields, staking, swaps, lending, and LP risk. No redundant tools and the count feels right for the purpose.
The tools cover key DeFi decision-making areas, but lack obvious operations like portfolio tracking, historical yields, or transaction execution. Some overlap exists between yields and lending rates, but the core dashboard needs are mostly addressed.