Skip to main content
Glama

L2 yield scanner

l2_yield_scanner
Read-only

Scan DeFi yields across L2 chains (Arbitrum, Optimism, Base, Polygon, zkSync, Linea, Scroll, Blast). Returns top pools sorted by APY with TVL, protocol, and per-chain summaries. Uses DeFi Llama data. Costs $0.005 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "l2_yield_scanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoFilter by L2 chain (e.g. 'arbitrum', 'optimism', 'base', 'polygon'). Omit for all L2s.
limitNoMax results (default: 25)
minTvlNoMinimum TVL in USD (default: 100,000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only and open-world access, but the description adds genuinely non-derivable behavior: the upstream source is DeFi Llama, results are APY-sorted, and each call costs $0.005 USDC. Cost disclosure in particular is high-value context an annotation would never carry. It omits rate limits and empty-result behavior, keeping it short of a 5.

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?

Four short sentences, front-loaded with the action and scope, then returns, then data source, then price. Every sentence adds distinct information with no repetition of the name or title.

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?

No output schema exists, so the description properly compensates by describing the return contents (APY, TVL, protocol, per-chain summaries). It also covers data provenance and cost, which is enough to call it correctly. Minor gaps remain around pagination and what an empty L2 result looks like.

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 the schema already documents chain, limit, and minTvl with defaults; baseline is 3. The description does add the complete eight-chain enumeration versus the schema's four illustrative examples, but it says nothing about limit or minTvl behavior beyond what structured fields provide.

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

Purpose4/5

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

Specific verb+resource ('Scan DeFi yields') with an explicit scope (L2 chains, enumerated) and stated return shape ('top pools sorted by APY with TVL, protocol, and per-chain summaries'). An agent knows exactly what this does. It stops short of 5 because it never names or contrasts itself with the sibling yield_rates, which plausibly overlaps.

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?

The L2-only scope implies when to reach for this rather than a general yield tool, and the chain list makes the boundary visible. However, there is no explicit statement of when-not-to-use it or which sibling to prefer for non-L2 yields, so usage must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources