defi-yields-mcp
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_yield_poolsA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_yields | Generate a prompt to analyze DeFi yield pools, optionally filtered by chain or project. Args: chain: Optional blockchain filter project: Optional project filter |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'get_yield_pools' has a clearly defined singular purpose of fetching DeFi yield pools with optional filters.
The single tool name 'get_yield_pools' follows a clear verb_noun pattern that would be consistent if there were more tools. There are no naming inconsistencies to evaluate in a one-tool set.
A single tool is insufficient for comprehensive DeFi yield analysis. While the tool provides basic fetching capabilities, the domain suggests needs for additional operations like historical data, comparisons, or pool-specific details that are missing.
The tool surface is severely incomplete for DeFi yield analysis. It only offers data fetching without any CRUD operations, filtering by more parameters like risk or type, or analytical tools for processing the yield data, leaving significant gaps for agent workflows.