Skip to main content
Glama

Stratalize Intelligence

Get Crypto Correlation Benchmark

get_crypto_correlation_benchmark
Read-only

30-day rolling correlation matrix for BTC, ETH, and SOL — Pearson correlation pairs, beta to BTC, dominance context, and portfolio diversification signal. Source: DeFiLlama historical prices. For crypto portfolio agents. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

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

Input Schema

NameRequiredDescriptionDefault
periodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The description goes meaningfully beyond the annotations by disclosing the upstream source, that it is live, the 503/no-charge failure behavior, and the $0.10 USDC x402 price, plus a data_source provenance field. However, it claims the provenance values are fred_api/fred_csv/fred_mixed while also naming DeFiLlama as the source, an internal inconsistency that could mislead an agent interpreting results. The 503 no-charge condition is also stated twice in slightly different phrasing.

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

Conciseness5/5

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

Wait — recalc: front-loading is good and the returned fields are listed early, but the definition contains a duplicated 503/no-charge clause and a provenance sentence that is irrelevant or wrong for a DeFiLlama-sourced tool, so there is wasted, potentially confusing 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?

With no output schema, the description does the right thing by enumerating returned fields, which is the main completeness win. But the period parameter is left unexplained and the provenance statement is contradictory, so an agent still has gaps about how to parameterize the call and how to interpret the data_source field.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'period' parameter, so the description carries the burden — but it repeatedly frames the output as a '30-day' matrix while the enum permits 7d and 90d, and never explains what changing the window does. The stated fixed window arguably conflicts with the parameter rather than clarifying it.

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 names the concrete resource and scope: a rolling correlation matrix for BTC, ETH, and SOL, with enumerated outputs (Pearson pairs, beta to BTC, dominance context, diversification signal). It also states the data source (DeFiLlama historical prices), so an agent knows exactly what the tool returns. It does not differentiate itself from nearby siblings such as get_verify_crypto_price or get_defi_yield_benchmark, leaving that to the agent's inference.

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 only usage context is 'For crypto portfolio agents,' which implies an audience but never states when to choose this over a price-verification or yield benchmark tool. There are no exclusions or prerequisites, and nothing explains which period window to pick for a given analysis.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources