Skip to main content
Glama

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
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the upstream source (DeFiLlama), the pricing model ($0.10 USDC per call), and the concrete failure contract (HTTP 503 with no charge when >50% of fields are unavailable) — genuinely useful context an agent cannot get from annotations. It loses a point for the self-contradictory provenance note listing 'fred_api/fred_csv/fred_mixed' for a tool whose stated source is DeFiLlama, which muddies rather than clarifies behavior.

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?

Purpose is front-loaded and the output list is efficient, but the 503/no-charge statement is repeated verbatim twice and the x402 pricing/provenance tail reads like boilerplate appended from other tools. Roughly a quarter of the text could be cut without loss.

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?

There is no output schema, and the description does compensate by enumerating the returned fields and the failure mode, which is the right instinct. However, it leaves the period parameter unexplained and carries an inconsistent data_source claim, so it is not fully complete for a tool with a selectable window and paid invocation.

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?

The single parameter (period: 7d/30d/90d) has 0% schema description coverage, and the description never explains it — it instead describes a fixed 30-day window, which mildly conflicts with the 7d/90d options. With the only parameter effectively undocumented in both places, the description does not compensate for the coverage gap.

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 a specific resource (30-day rolling correlation matrix for BTC, ETH, SOL) and enumerates the outputs (Pearson pairs, beta to BTC, dominance, diversification signal), which distinguishes it from siblings like get_verify_crypto_price and get_chain_tvl_benchmark. The only blemish is that it hardcodes '30-day' even though the tool exposes a period selector.

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?

'For crypto portfolio agents' states an audience rather than a usage condition; there is no explicit when-to-use or when-not-to-use guidance and no named alternative despite many adjacent crypto/benchmark siblings. An agent can infer the intended use from the listed outputs, but it must do the work itself.

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