Skip to main content
Glama

YieldSignal

by app.vercel.yieldsignal

get_exit_capacity

Exit capacity for a Base lending market: per-protocol utilization and withdrawable liquidity read from the protocol's own books (Aave, Compound), plus — if you pass amountUsd — whether that size can be withdrawn right now and what share of the market it would be. High APY at high utilization means the market pays well and will not let you out; this tool separates the two. Protocols that do not expose borrowed-vs-supplied are marked unmeasured and are never recommended as executable. USDC only for USD figures; WETH returns utilization without USD (no price oracle in the paid path).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNoWhich Base lending market to measure: USDC (full USD figures) or WETH (utilization only). Defaults to USDC.
amountUsdNoPosition size in USD to test for exit. Omit to get utilization and free liquidity without an exit verdict.

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries full burden and excels: it discloses the data source (protocol's own books), the optional exit verdict via amountUsd, limitations for WETH (no USD price oracle), and handling of unmeasured protocols. This is rich behavioral context.

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?

The description is dense but front-loaded with the core purpose. Every sentence contributes value, covering asset differences and limitations. Slightly long but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, this description provides a complete picture: what the tool does, how parameters affect behavior, key limitations (asset-specific, price oracle), and how it relates to yield concerns. It is sufficient for an AI agent to select and invoke this tool correctly.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds significant meaning: amountUsd is explained as testing withdrawal feasibility and market share, and asset differences between USDC and WETH are clarified beyond the enum descriptions.

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's function: measuring exit capacity (utilization and withdrawable liquidity) for a Base lending market. It distinguishes itself from yield-focused sibling tools by focusing on exit capacity and separating it from APY.

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

Usage Guidelines4/5

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

The description implies usage context: it helps when high APY at high utilization needs to be separated from actual exit capacity. It also notes that unmeasured protocols are never recommended, providing guidance on when not to rely on this tool. However, it doesn't explicitly name alternative sibling tools.

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

All YieldSignal toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Each tool targets a distinct analytical question (current yield, sustainability, decision, rate sensitivity, exit liquidity). The descriptions are detailed and clearly separate the tools, though get_exit_capacity and get_rate_sensitivity both involve utilization and could be superficially confused by an agent.

Naming Consistency5/5

All tools follow a consistent 'get_' verb-noun pattern, with descriptive nouns like 'yield_signal', 'yield_durability', 'yield_decision', 'rate_sensitivity', and 'exit_capacity'. The pattern is predictable and readable.

Tool Count5/5

Five tools is well-scoped for a specialized yield analytics server. Each tool earns its place by covering a distinct aspect of yield assessment, avoiding bloat while providing sufficient functionality.

Completeness4/5

The set covers the core yield analysis lifecycle: signal, durability, decision, rate sensitivity, and exit capacity. Minor gaps exist, such as no explicit tool for historical comparisons or protocol discovery, but the described tools handle the main workflows.

Resources