Skip to main content
Glama
Sign In
MetaVault MCP

MetaVault MCP

by Finanzgoblin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pendle_get_market_history

Retrieve historical data for a Pendle market to analyze trends in APY, TVL, volume, and prices over time for yield stability assessment and anomaly detection.

Instructions

Historical time-series data for a Pendle market.

Shows how implied APY, TVL, volume, PT/YT prices, and other metrics have moved over time. The first tool that answers "what happened?" not just "what is it now?"

Enables: trend analysis, yield stability assessment, anomaly detection, conviction building before entry. A flat APY with low stddev means predictable yield. A volatile APY with high stddev means the rate you see today may not persist.

Available fields: impliedApy, tvl, tradingVolume, ptPrice, ytPrice, baseApy, lpPrice, lpRewardApy, maxApy, pendleApy, swapFeeApy, syPrice, totalPt, totalSupply, totalSy, totalTvl, underlyingApy, underlyingInterestApy, underlyingRewardApy, voterApr, ytFloatingApy, lastEpochVotes

Use pendle_get_market_details for current market snapshot. Use pendle_list_markets to find market addresses.

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>"
    },
    "name": "pendle_get_market_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesThe blockchain network where the Pendle market lives.
market_addressYesThe Pendle market/pool contract address.
periodNoTime period: 7d (hourly), 30d (daily), 90d (daily), 1y (weekly). Default 30d.30d
fieldsNoComma-separated fields to include. Default: impliedApy,tvl,tradingVolume,ptPrice,ytPrice. Use 'all' for everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It explains the tool is for historical data, lists available fields, and provides interpretation guidance. It does not explicitly state it is a read-only operation, but the context implies it.

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 informative but not overly verbose. It uses bullet-like listing for fields and provides context on interpretation. Could be slightly more structured with separate sections, but it is efficient.

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 no output schema, the description explains the return data (time-series of metrics), provides interpretation guidance, and mentions the default period. It is complete enough for an agent to understand what the tool does and how to use it.

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%, so baseline is 3. The description adds value by listing all available fields in text, explaining the default period, and clarifying that 'all' can be used for the fields parameter. This goes beyond just repeating schema 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 it returns 'historical time-series data for a Pendle market' with specific metrics. It distinguishes itself from sibling tools like pendle_get_market_details (current snapshot) and pendle_list_markets (find addresses).

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?

Explicitly tells when to use this tool ('trend analysis, yield stability assessment') and provides alternatives ('Use pendle_get_market_details for current market snapshot. Use pendle_list_markets to find market addresses.').

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

Deploy Server

Other Tools