Skip to main content
Glama
@atlasyield/mcp

@atlasyield/mcp

Get vault score

get_vault_score
Read-onlyIdempotent

Retrieve a vault's Atlas Score, including composite and pillar scores, live APY/TVL, data quality, and timestamp to assess vault quality before deposit decisions.

Instructions

Latest Atlas Score for one vault: composite (0-100), label, the four pillar scores (yield, safety, liquidity, sustainability), live APY/TVL, data quality and the scoring timestamp. Each vault also carries holdingsScore: the score from what it holds, with its cap; published:false means it is not yet the headline composite. notYieldProduct: true means it earns essentially nothing; do not present the score as a reason to deposit for yield. Returns found:false when the vault is not in the scored universe. 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": {
      "chainId": "<chainId>",
      "address": "<address>"
    },
    "name": "get_vault_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesVault contract address (0x…); case-insensitive
chainIdYesEVM chain id, e.g. 1 (Ethereum), 8453 (Base), 42161 (Arbitrum)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so 'Read-only' in the description is redundant. Beyond that, it discloses meaningful behavior: 'found:false' for vaults outside the scored universe, 'published:false' meaning the composite is not yet headline, and the capped holdingsScore. It stops short of coverage/auth or freshness details, so it lands at 4 rather than 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?

Front-loaded with the resource and its return payload, then terse field-semantics clauses. Dense but every clause conveys a distinct fact; the only waste is the redundant 'Read-only.' at the end.

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?

There is no output schema, so the description must carry the return values and it does so thoroughly, including edge cases (found:false, unpublished composites, capped holdingsScore). Minor gaps remain, e.g. what 'label' values exist or what 'data quality' means in practice, but an agent could call this correctly.

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%, with both address and chainId documented including examples and case-sensitivity, so the schema carries the parameter burden. The description adds no additional meaning about the parameters, 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?

Names a specific verb+resource ('Latest Atlas Score for one vault') and enumerates exactly what is returned: composite 0-100, label, four pillar scores, APY/TVL, data quality, timestamp. It does not explicitly distinguish itself from the similarly-named sibling explain_vault_score, so it falls 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 Guidelines3/5

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

Gives field-level usage instructions ('do not present the score as a reason to deposit for yield' when notYieldProduct is true), which is real guidance about how to use the result. However, it never says when to call this versus explain_vault_score or compare_vaults, and offers no exclusions or prerequisites.

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