Skip to main content
Glama
@atlasyield/mcp

@atlasyield/mcp

Compare vaults

compare_vaults
Read-onlyIdempotent

Compares 2-8 vaults side by side for composite and pillar Atlas Scores, live APY/TVL, yield quality and exit safety, returning a composite ranking and flagging unscored vaults.

Instructions

Side-by-side Atlas Scores for 2-8 vaults: composite, label, four pillars, live APY/TVL, data quality, yieldQuality and exitSafety, with a ranking by composite, vaults flagged notYieldProduct ranked after the others (each entry also has notYieldProduct: true when the vault earns about nothing; null when the API does not report it). Unscored vaults come back found:false rather than silently dropped. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vaults": "<vaults>"
    },
    "name": "compare_vaults"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaultsYes2-8 vaults to compare, any mix of chains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the bar is lower, yet the description still adds real behavior: results are ranked by composite, notYieldProduct vaults are ranked after the others, that flag is null when the API does not report it, and unscored vaults return found:false instead of being dropped. It does not cover failure modes such as invalid addresses or rate limits, and the trailing 'Read-only.' merely restates the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key information (what is compared, count range) is front-loaded, but the single sentence is dense and run-on, stacking output fields, ranking rules and flag semantics into one clause chain. The closing 'Read-only.' repeats the readOnlyHint annotation and does not earn 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 full burden of describing return values, and it does so well: composite ranking, flag ordering, null semantics, and found:false for unscored vaults. For a single-parameter read-only tool that is nearly complete, with only error/edge-case behavior for malformed vault identifiers left unstated.

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% and the single parameter is fully documented, including minItems/maxItems and 'any mix of chains'. The description's '2-8 vaults' and chain-mixing remarks duplicate rather than extend the schema, so this sits at the 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?

The description opens with a specific verb and resource ('Side-by-side Atlas Scores for 2-8 vaults') and enumerates exactly what is compared (composite, label, four pillars, APY/TVL, yieldQuality, exitSafety). That clearly separates it from single-vault siblings like get_vault_score or explain_vault_score, though no sibling is named explicitly.

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?

The 2-8 vault framing implies when the tool applies (multi-vault comparison) and the minItems/maxItems constraint reinforces it, but there is no explicit statement of when to prefer this over get_vault_score or explain_vault_score, and no when-not guidance or prerequisites.

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