Skip to main content
Glama
@atlasyield/mcp

@atlasyield/mcp

Find vaults

find_vaults
Read-onlyIdempotent

Find ranked vaults for an asset on a chain when you lack a vault address, with live APY, TVL, risk flags, deposit routability, and filtered-out reasons.

Instructions

Start here when you do not already have a vault address. Answers "which vaults for this asset on this chain?": returns a short ranked list (default 5, max 10) of scored vaults with composite, label, live APY/TVL, risk flags (thin_tvl, apy_outlier, no_yield, ...), whether a deposit can reach it (routable), and a citable page URL. It also returns what the filters REMOVED: counts per filter, the best-ranked dropped vaults with reasons, near-miss asset symbols, and whether more matched than were returned. Vaults with no deposit route and rows scored on fallback data are excluded. Ranked by the chosen metric, a ranking and not a recommendation. A flag is a caution, not a verdict, and no flag does not mean safe. Take a chosen vaultId/address to check_route_survival before any deposit. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
assetNoUnderlying asset symbol, or a list of up to 10, e.g. USDC or ["USDC","USDT0"]. Exact match: USDC does not include syrupUSDC (similarAssets lists near misses)
chainNoChain name (base, ethereum, arbitrum, optimism, bnb, solana) or EVM chain id
limitNoRows to return, default 5, max 10
minApyNoMinimum live APY in percentage points, e.g. 10 for 10%
sortByNoRank by this, descending. Default composite
minScoreNoMinimum Atlas composite (0-100)
minTvlUsdNoMinimum live TVL in USD
protocolIdNoProtocol slug, e.g. morpho, aave-v3, pendle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • addedInput schema / properties / asset / anyOf
      Added value: +[
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "maxItems": 10,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / asset / description
      Previous value: -"Underlying asset symbol, e.g. USDC, WETH, USDT"New value: +"Underlying asset symbol, or a list of up to 10, e.g. USDC or [\"USDC\",\"USDT0\"]. Exact match: USDC does not include syrupUSDC (similarAssets lists near misses)"
    • removedInput schema / properties / asset / minLength
      Removed value: -1
    • removedInput schema / properties / asset / type
      Removed value: -"string"
    • addedInput schema / properties / minApy
      Added value: +{
      +  "description": "Minimum live APY in percentage points, e.g. 10 for 10%",
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. Addedv0.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered; the description goes well beyond it. It discloses exclusion rules (no deposit route, rows scored on fallback data), result caps, and unexpected output (per-filter removal counts, dropped vaults with reasons, near-miss symbols, truncation flag), which an agent cannot infer from structured fields.

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?

Entry condition, return shape, exclusions, caveats, and next step are front-loaded and each sentence adds information. It is dense and slightly overpacked with parenthetical caveats, but not padded.

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?

There is no output schema, so the description carries the full burden of describing return values, and it does so concretely, including negative-result reporting and truncation signaling. For an 8-parameter discovery tool this is complete enough to call correctly on the first attempt.

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 the baseline is 3, but the description adds real meaning: it explains that filter parameters also drive 'what was REMOVED' reporting and that ranking follows 'the chosen metric'. That connects parameters to output behavior rather than restating field docs.

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?

States a specific verb and resource and frames the exact question answered: 'which vaults for this asset on this chain?'. It enumerates the return payload (composite, label, live APY/TVL, risk flags, routability, citable URL), which separates it from score-explanation and comparison siblings.

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

Usage Guidelines4/5

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

'Start here when you do not already have a vault address' gives an explicit entry condition, and 'Take a chosen vaultId/address to check_route_survival before any deposit' names the follow-up tool. It does not explicitly name the alternative for agents that already hold an address (e.g. explain_vault_score), leaving that half of the routing implicit.

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