Skip to main content
Glama

yield_scan

πŸ”’ PREMIUM (not available anonymously on this endpoint): Deep scan a specific pool or token β€” APY breakdown (base + reward), TVL, risk score, IL exposure, 30d average. Search by name, symbol, or pool ID.

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": "yield_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoToken or protocol name (e.g. 'USDC', 'aave')
pool_idNoDeFiLlama pool ID for exact match

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does disclose the critical auth constraint: the tool is premium and 'not available anonymously on this endpoint,' which is exactly the kind of gating an agent must know before calling. It also enumerates the returned data (compensating for the absent output schema), but says nothing about ambiguous matches, no-result behavior, or error cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense sentence that front-loads the most decision-relevant fact (premium/anonymous-unavailable) before the capability and return fields. Nothing is wasted, though the emoji and stacked field list make it slightly harder to parse at a glance.

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 two-optional-param lookup tool with no annotations and no output schema, the description supplies the two things that matter most: the access restriction and the shape of the returned data. The remaining gap is resolution behavior (what happens with no match, partial matches, or both parameters set), which an agent would have to discover by trial.

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 description coverage is 100%, so both parameters are already fully documented, including examples and the meaning of pool_id as an exact-match key. The description's 'Search by name, symbol, or pool ID' restates the schema rather than adding new meaning, and it does not clarify how query and pool_id interact when both are supplied. Baseline 3 applies.

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?

The description gives a specific verb ('Deep scan') and resource ('a specific pool or token') and enumerates what it returns (APY breakdown, TVL, risk score, IL exposure, 30d average). The phrase 'a specific pool or token' implicitly separates it from aggregate siblings like top_yields and chain_yields, though none are named explicitly.

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?

Usage is only implied: call this when you need deep detail on one pool or token rather than a list. The 'Search by name, symbol, or pool ID' line explains how to address the target but not when to prefer this over yield_compare or risk_adjusted, and no alternatives or exclusions are stated.

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.