Skip to main content
Glama

Philidor DeFi Vault Risk Analytics

by io.philidor
OverviewDiscussionsAdmin

search_vaults

Search and filter DeFi vaults by chain, protocol, asset, risk tier, TVL, and more. Returns a paginated list with risk scores and APR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNoFilter by asset symbol (e.g. USDC, WETH)
chainNoFilter by chain name or slug (e.g. Ethereum, Base, Arbitrum, Solana)
limitNoMax results (default 10, max 50)
queryNoSearch by vault name, symbol, asset, protocol, or curator
minTvlNoMinimum TVL in USD
sortByNoSort field: tvl_usd, apr_net, name, last_synced_at
protocolNoFilter by protocol ID: aave, morpho, spark, compound, yearn, beefy, uniswap, nest, maple, kamino. Aave V4 is protocol=aave plus protocolVersion=v4 (aave-v4 is accepted as an alias).
riskTierNoFilter by risk tier: Prime, Core, or Edge
sortOrderNoSort order: asc or desc
depositableNoFilter by current ability to accept new deposits. When true, vaults whose depositability is not yet indexed are still included; when false, only vaults whose maxDeposit on-chain is zero (caps reached, paused, or supply queue saturated) are returned.
protocolVersionNoFilter by protocol generation: v3, v4, v3-lido, v3-horizon, klend, kvault. Required to isolate Aave V4 (protocol=aave, protocolVersion=v4). Vaults list this as protocol_version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / protocol / description
      Previous value: -"Filter by protocol ID (e.g. morpho, aave, aave-v4, yearn, beefy, spark, compound, uniswap, nest, maple, kamino)"New value: +"Filter by protocol ID: aave, morpho, spark, compound, yearn, beefy, uniswap, nest, maple, kamino. Aave V4 is protocol=aave plus protocolVersion=v4 (aave-v4 is accepted as an alias)."
    • addedInput schema / properties / protocolVersion
      Added value: +{
+  "description": "Filter by protocol generation: v3, v4, v3-lido, v3-horizon, klend, kvault. Required to isolate Aave V4 (protocol=aave, protocolVersion=v4). Vaults list this as protocol_version.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / protocol / description
      Previous value: -"Filter by protocol ID (e.g. morpho, aave, aave-v4, yearn, beefy, spark, compound, nest)"New value: +"Filter by protocol ID (e.g. morpho, aave, aave-v4, yearn, beefy, spark, compound, uniswap, nest, maple, kamino)"
  3. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"Filter by chain name (e.g. Ethereum, Base, Arbitrum)"New value: +"Filter by chain name or slug (e.g. Ethereum, Base, Arbitrum, Solana)"
  4. Changed1 schema field changed
    • changedInput schema / properties / protocol / description
      Previous value: -"Filter by protocol ID (e.g. morpho, aave-v3, yearn-v3)"New value: +"Filter by protocol ID (e.g. morpho, aave, aave-v4, yearn, beefy, spark, compound, nest)"
  5. Changed1 schema field changed
    • addedInput schema / properties / depositable
      Added value: +{
+  "description": "Filter by current ability to accept new deposits. When true, vaults whose depositability is not yet indexed are still included; when false, only vaults whose maxDeposit on-chain is zero (caps reached, paused, or supply queue saturated) are returned.",
+  "type": "boolean"
+}
  6. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that results are paginated and include risk scores and APR, which is useful return-shape context, but it omits permission requirements, any rate limits, and default/max page behavior (left to the schema).

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?

Two tight sentences with the primary action front-loaded and no filler. The trailing 'and more' is mildly vague but does not bloat the text.

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 an 11-parameter tool with no annotations and no output schema, the description does partially compensate by stating the return contents (paginated list with risk scores and APR). However, it gives no routing guidance among the numerous sibling tools and no behavioral caveats, leaving meaningful gaps.

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 description coverage is 100%, so each of the 11 parameters is already documented with examples and defaults in the schema. The description only name-drops the same filter categories without adding syntax or semantics beyond the schema, which is the expected baseline.

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 verb and resource ('Search and filter DeFi vaults') and enumerates the filter dimensions (chain, protocol, asset, risk tier, TVL), so the agent knows exactly what the tool does. It does not distinguish itself from siblings like find_safest_vaults, compare_vaults, or list_vaults_with_incidents, so it stops short of 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 Guidelines2/5

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

There is no explicit guidance on when to use this tool versus the many sibling search/retrieval tools (find_safest_vaults, compare_vaults, get_vault, get_vault_risk_breakdown). Usage is only implied by the word 'search', and no exclusions or prerequisites are given.

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

All Philidor DeFi Vault Risk Analytics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources