Skip to main content
Glama

pendle_get_looping_strategy

Calculate leveraged fixed-yield strategy using Pendle PT as Morpho collateral to borrow, reinvest, and multiply yield exposure with risk analysis.

Instructions

Calculate a leveraged fixed-yield strategy using Pendle PT + Morpho looping.

Strategy: Buy Pendle PT → use as Morpho collateral → borrow underlying → buy more PT → repeat. Each loop multiplies yield exposure.

Returns projected yields at different leverage levels (1x to max safe leverage), effective APY, risk parameters, borrow rate sensitivity, and break-even analysis.

Automatically fetches the live Morpho borrow rate and LLTV when a matching market exists.

NOTE: Looping requires a Morpho market that accepts the specific Pendle PT as collateral. Morpho markets for Pendle PTs exist primarily on Ethereum mainnet and some on Arbitrum.

The Pendle equivalent of spectra_get_looping_strategy.

Use pendle_get_market_details for full market info. Use pendle_scan_opportunities(include_looping=true) for cross-market looping rankings. Use morpho_list_markets to find available Morpho markets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesThe blockchain network
market_addressYesThe Pendle market address
morpho_ltvNoOverride Morpho LTV ratio (e.g. 0.86). Auto-detected if omitted.
borrow_rateNoOverride Morpho borrow rate in % APY. Fetched live if omitted.
max_loopsNoMaximum loop iterations (default 5)
Behavior4/5

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

The description discloses key behaviors: auto-fetches live Morpho borrow rate and LLTV, calculates projected yields at different leverage levels, and explains the looping strategy. It does not explicitly state read-only nature or rate limits, but no annotations are provided so the description carries the burden.

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 well-structured with a clear summary, strategy explanation, outputs, note, and alternative tool references. It is slightly verbose but every sentence contributes value, earning a 4.

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?

Despite no output schema, the description explicitly lists return values (projected yields, effective APY, risk parameters, etc.). It covers prerequisites, auto-fetching, and alternative tools, making it complete for a tool with 5 parameters and 2 required.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for all parameters. The description adds meaning beyond schema by explaining that morpho_ltv and borrow_rate are overrides with auto-detection, and max_loops defaults to 5. This adds useful context.

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 calculates a leveraged fixed-yield strategy using Pendle PT + Morpho looping, explains the strategy, and explicitly distinguishes from sibling tools like pendle_get_market_details and pendle_scan_opportunities.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use and when-not-to-use guidance, including alternative tools (pendle_get_market_details, pendle_scan_opportunities, morpho_list_markets) and prerequisites (requires Morpho market accepting PT).

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/Finanzgoblin/spectra-mcp-server'

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