Skip to main content
Glama

AINDEX

Pendle markets: fixed and floating yield

list_pendle_markets
Read-only

Every active Pendle market on Robinhood Chain: the implied fixed rate (what buying PT locks in to expiry), the floating yield's range, LP yield, liquidity and expiry.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds substantive behavioral context beyond that: results are limited to active markets only, confined to Robinhood Chain, and include the specific yield/liquidity/expiry attributes an agent will actually receive. It does not disclose ordering, result count, or data freshness, which keeps it from a 5.

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?

A single front-loaded sentence with no filler; the scope comes first and the returned fields follow as a compact list. The parenthetical explaining what the implied fixed rate means is useful but dense; otherwise every clause earns its place.

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?

With no output schema, the description carries the burden of telling the agent what comes back, and it does so by naming the five categories of market data. For a zero-parameter listing tool that is close to sufficient, with only volume, ordering, and per-market detail-vs-summary framing left implicit.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends its words on scope and returned fields rather than inventing filter semantics that do not exist.

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?

States a specific resource and scope: "Every active Pendle market on Robinhood Chain", then enumerates the data points returned (implied fixed rate, floating yield range, LP yield, liquidity, expiry). An agent can tell this is a Pendle-market listing and not Morpho/Lighter market data without opening a schema. It stops short of naming a sibling, so 4 rather than 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 implied by the scope phrase "active Pendle markets on Robinhood Chain", so an agent knows this is a discovery/listing call for a specific venue. There is no explicit when-to-use vs. when-not guidance, no mention of alternatives such as list_pools or list_assets, and no note on when a per-market detail call would be preferred.

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.

Resources