SiteCheck Crypto & Finance

Pendle Finance active yield markets on Ethereum: name

finance_pendle_finance_markets_v2

Read-only

Pendle Finance active yield markets on Ethereum: name, expiry date, implied APY, aggregated APY and liquidity, from Pendle's public v2 API. Sorted as Pendle returns them; use limit to cap the list. Related tools on this server, for a different need: finance_curve_finance_pools when you need Curve Finance pools on Ethereum: pool name, total USD value; crypto_aave_lending_markets when you need Aave v3 Ethereum main-market reserves: supply and borrow. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
`limit`	No	How many markets, 1 to 50 (default 10)

Output Schema

Name	Required	Description	Default
`total`	No
`source`	No
`markets`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond readOnlyHint and openWorldHint, it discloses the external source (Pendle public v2 API), ordering (Pendle's order), page-size cap via limit, and pricing ($0.002 USDC per successful x402 call, failures not charged). These are material operational details an agent would not get from annotations alone.

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?

The purpose and returned fields are front-loaded, followed by sorting and limit behavior, alternatives, and cost. The paragraph is dense but each sentence carries selection or billing information, with no redundant restatement of the schema.

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?

For a read-only, single-parameter list tool with an output schema and clear annotations, the description supplies everything needed: scope, fields, ordering, limit behavior, sibling routing, and cost. No significant completeness gap remains.

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?

There is only one parameter, and the schema already documents it fully, including the 1–50 range and default of 10. The description adds only the general instruction to use limit to cap the list, which is baseline-level with 100% schema coverage.

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?

Describes a specific resource—active Pendle v2 yield markets on Ethereum—and lists the returned fields such as name, expiry, implied APY, aggregated APY, and liquidity. It also distinguishes this from named siblings for Curve pools and Aave reserves, so an agent can select it without opening the schema.

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?

Gives explicit alternatives for different needs: finance_curve_finance_pools for Curve pools and crypto_aave_lending_markets for Aave reserves. Combined with the first sentence, this makes the when-to-use and when-not-to-use boundary clear, and it tells the caller to use limit to cap the list.

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

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?