Skip to main content
Glama

top_yield_farms

Find top DeFi yield farms from the last 24 hours with realistic APY, risk notes, and TVL. Filter by asset or minimum APY.

Instructions

Latest 24h top DeFi yield farm picks with realistic APY (emissions stripped), risk notes, TVL, protocol. Sourced from FalsifyLab daily aggregator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomax results (1-50)
min_apyNofilter floor in pct
assetNofilter by asset symbol (BTC, ETH, SOL, etc.)

Implementation Reference

  • Tool registration with name 'top_yield_farms', description, and input schema (limit, min_apy, asset filters).
    TOOLS = [
        {
            "name": "top_yield_farms",
            "description": "Latest 24h top DeFi yield farm picks with realistic "
                           "APY (emissions stripped), risk notes, TVL, protocol. "
                           "Sourced from FalsifyLab daily aggregator.",
            "inputSchema": {
                "type": "object",
                "properties": {
                    "limit": {"type": "integer", "default": 10,
                               "description": "max results (1-50)"},
                    "min_apy": {"type": "number", "default": 0,
                                 "description": "filter floor in pct"},
                    "asset": {"type": "string",
                               "description": "filter by asset symbol (BTC, ETH, SOL, etc.)"},
                },
            },
        },
  • Input schema for top_yield_farms: limit (int, default 10), min_apy (number, default 0), asset (string filter).
    "inputSchema": {
        "type": "object",
        "properties": {
            "limit": {"type": "integer", "default": 10,
                       "description": "max results (1-50)"},
            "min_apy": {"type": "number", "default": 0,
                         "description": "filter floor in pct"},
            "asset": {"type": "string",
                       "description": "filter by asset symbol (BTC, ETH, SOL, etc.)"},
        },
    },
  • Tool dispatch handler: calls _api_get('/api/yield/top', args) to fetch yield farm data from the FalsifyLab API.
    if name == "top_yield_farms":
        return _api_get("/api/yield/top", args)
  • Helper function _api_get that makes HTTP GET requests to the FalsifyLab backend API with authorization and error handling.
    def _api_get(path: str, params: dict | None = None) -> dict:
        if params:
            from urllib.parse import urlencode
            path = f"{path}?{urlencode(params)}"
        req = urllib.request.Request(
            f"{API_BASE}{path}",
            headers={
                "User-Agent": USER_AGENT,
                "Accept": "application/json",
                **({"Authorization": f"Bearer {API_KEY}"} if API_KEY else {}),
            },
        )
        try:
            with urllib.request.urlopen(req, timeout=20) as r:
                return json.loads(r.read())
        except urllib.error.HTTPError as e:
            body = e.read().decode(errors="ignore")[:400]
            return {"error": f"HTTP {e.code}: {body}"}
        except Exception as e:
            return {"error": str(e)[:200]}
Behavior3/5

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

With no annotations, the description carries full burden. It mentions 'realistic APY (emissions stripped)' and 'risk notes', hinting at data processing, but does not detail calculation methods, data freshness beyond '24h', error handling, or potential limitations. Adds some context but lacks comprehensive behavioral disclosure.

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?

Two concise sentences that front-load the main purpose and key features. No extraneous information. Every sentence adds value.

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?

For a simple list tool with 3 optional parameters and no output schema, the description covers purpose, data source, and key outputs. However, it lacks explanation of risk notes derivation, default limit, or pagination behavior. Could be more complete but is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description does not mention any parameters (limit, min_apy, asset) or explain their purpose beyond what the schema already provides. No added value over schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns 'top DeFi yield farm picks' with specific attributes like 'realistic APY (emissions stripped), risk notes, TVL, protocol'. It specifies 'latest 24h' and the data source 'FalsifyLab daily aggregator', which distinguishes it from sibling tools like 'active_airdrop_farms'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies use for yield farming recommendations, it does not explicitly state when to use this tool versus alternatives like 'active_airdrop_farms' or provide any conditions or limitations. No guidance on prerequisites or exclusions.

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/FalsifyLab/falsifylab-alpha-mcp'

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