Skip to main content
Glama

morpho_list_vaults

List vaults on any chain to discover supply-side liquidity. Returns details including AUM, APY, fees, curator info, and market allocations.

Instructions

List Morpho vaults on a chain — discover where supply-side liquidity lives. Returns vault details including AUM, APY, fees, curator info, and market allocations.

Morpho vaults are curated lending strategies managed by curators who allocate deposits across lending markets. They are often (but not always) the primary source of supply-side liquidity for PT looping markets. EOA suppliers also exist.

Protocol context:

  • Vault APY comes from lending yield on allocated markets, minus the curator's fee. High APY could indicate high borrow demand or could reflect temporary incentives.

  • A vault's allocation breakdown shows which markets it supplies and how much capital is deployed to each. A vault allocating to a PT market directly funds the looping pool.

  • Supply cap (when present) limits how much a vault will deploy to a given market. Uncapped allocations track demand; capped allocations create a ceiling.

  • Not all vaults on a chain allocate to PT markets — many serve non-PT markets. Use morpho_get_market_suppliers with a specific market key to find who actually supplies it.

Use morpho_get_market_suppliers to see who supplies a specific market. Use morpho_list_markets to find available PT lending markets. Use spectra_get_looping_strategy to model leveraged yield after identifying supply liquidity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesThe blockchain network to query
asset_filterNoFilter by asset symbol (e.g., 'USDT', 'USDC'). Matches vault names/assets.
min_tvl_usdNoMinimum vault AUM in USD (default 0)
top_nNoNumber of vaults to return (default 20, max 50)
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses return fields (AUM, APY, fees, curator info, market allocations) and explains vault allocation dynamics (supply caps, uncapped allocations). Slightly lacks explicit statement that operation is read-only, but implied by context.

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?

Well-structured with a clear purpose statement first, followed by protocol context and usage notes. Slightly lengthy but all sentences add value.

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?

Completeness is high given no output schema: describes return fields, explains APY derivation, supply caps, and how vaults relate to PT markets. Also situates tool within broader protocol ecosystem.

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?

Schema coverage is 100%, so baseline is 3. Description does not add semantic detail beyond schema; it provides protocol context but not parameter-specific meaning.

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?

Clearly states 'List Morpho vaults on a chain' with verb and resource, and explicitly distinguishes from sibling tools like morpho_get_market_suppliers and morpho_list_markets by referencing them.

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?

Provides explicit when-to-use guidance ('discover where supply-side liquidity lives') and when-not-to ('Not all vaults... allocate to PT markets'). Lists three specific alternatives: morpho_get_market_suppliers, morpho_list_markets, spectra_get_looping_strategy.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Finanzgoblin/spectra-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server