Skip to main content
Glama

DeFi Funding Arbitrage, Pendle & Prediction Odds MCP

Compare Pendle Fixed APY vs Perp Funding Carry

compare_pendle_fixed_vs_funding
Read-onlyIdempotent

Compares $3M+ TVL Pendle fixed-rate Principal Token (PT) implied APYs against live Hyperliquid perpetual funding carry benchmarks.

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

Input Schema

NameRequiredDescriptionDefault
stablecoinOnlyNoFilter to stablecoin Pendle pools only (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value by naming the data sources (Pendle PTs, live Hyperliquid funding) and the $3M+ TVL inclusion threshold, but says nothing about data freshness, refresh cadence, or what the comparison output looks like.

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?

One front-loaded sentence that identifies the compared quantities and the scope qualifier with no filler. It is efficiently sized, though the density of jargon (PT, implied APY, funding carry) is packed without any structural aids.

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

Completeness3/5

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

For a cross-protocol analytics tool with no output schema, the definition explains the inputs it compares but not the shape of the result — whether it returns a ranked spread table, a single number, or per-pool rows. An agent knows what the tool is about but not what it will receive back.

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?

The single parameter stablecoinOnly is fully documented in the schema (100% coverage) but is never mentioned in the description, so no extra semantics such as how the filter interacts with the $3M+ threshold are added. Baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific comparison (Pendle fixed-rate PT implied APYs vs Hyperliquid perp funding carry) plus the TVL scope ($3M+), so the agent can tell what data is produced and that it is a cross-protocol comparison rather than a single-venue scan. It does not explicitly distinguish itself from the similar-sounding scan_perp_funding_spreads sibling, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the content of the comparison — an agent can infer it is for evaluating whether locked Pendle fixed yield beats floating funding carry. There is no when-to-use framing, no when-not, and no routing to alternatives such as scan_perp_funding_spreads or get_institutional_stable_yields.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.