MetaVault MCP

pendle_quote_trade

Estimate Pendle PT trade outcome with expected output, price impact, effective APY, and minimum output after slippage.

Instructions

Estimate expected output, price impact, and effective APY for a Pendle PT trade.

Uses the Pendle logit AMM model to estimate trade outcomes. Shows:

Expected output amount and effective rate
Price impact at your trade size
Effective APY after accounting for entry cost
Minimum output with slippage tolerance

Side:

"buy": Spend underlying/SY to get PT (lock in fixed rate)
"sell": Sell PT for underlying/SY (exit fixed position)

The Pendle equivalent of spectra_quote_trade.

Use pendle_get_market_capacity for a multi-size impact curve. Use pendle_get_market_details for full market information.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>",
      "market_address": "<market_address>",
      "amount": "<amount>",
      "side": "<side>"
    },
    "name": "pendle_quote_trade"
  }
}

Input Schema

Name	Required	Description
`chain`	Yes	The blockchain network
`market_address`	Yes	The Pendle market address
`amount`	Yes	Amount of input token (underlying/SY for buy, PT for sell)
`side`	Yes	"buy" = spend underlying to get PT; "sell" = sell PT for underlying
`slippage_pct`	No	Slippage tolerance in % (default 0.5%)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0May 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations provided, so the description fully bears the burden. It discloses the tool uses the Pendle logit AMM model and estimates outputs including slippage. It implies no side effects or destructive actions, which is appropriate for a quote tool.

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 moderately long but well-organized with bullet points for outputs, a clear side explanation, and sibling tool references. Every sentence adds value; no redundant or wasted text.

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?

Given the tool's complexity (trade estimation with slippage, APY), the description covers key outputs and parameter semantics. It references sibling tools for deeper analysis. No output schema exists, but the description lists expected outputs sufficiently.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds context for the side parameter (buy vs sell token types) and mentions default slippage, but this information is already in the schema. The description adds minimal extra meaning beyond what is already structured.

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 estimates expected output, price impact, and effective APY for a Pendle PT trade. It differentiates from siblings like pendle_get_market_capacity and pendle_get_market_details, and is explicitly linked as the Pendle equivalent of spectra_quote_trade.

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 explains the tool is for trade estimation and provides side semantics. It directs users to pendle_get_market_capacity for multi-size impact curves and pendle_get_market_details for full market info, offering clear alternatives. No explicit 'when not to use' but strong guidance.

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

Deploy Server