Skip to main content
Glama

TallyForge Quant Signals

Crypto Correlation Matrix

correlation_matrix

Pearson correlation matrix of daily log returns for 2-8 major crypto assets over a 30, 90 or 180-day window, with the most and least correlated pairs, annualized volatility per asset and beta vs BTC when BTC is included. Useful for diversification checks and pair selection.

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": {
      "symbols": "<symbols>"
    },
    "name": "correlation_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesComma-separated tickers (2-8), e.g. BTC,ETH,SOL
window_daysNo30, 90 or 180 (default 90)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the return content (matrix plus most/least correlated pairs, annualized volatility, beta) and a conditional behavior (beta only when BTC is included). It does not cover data source, latency/cost, or what happens with invalid tickers or a window value outside the three listed.

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?

Two sentences, front-loaded with the computation and scope, then the output inventory, then the use case. No filler or repetition; the density of output information is justified for a computation tool.

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?

For a two-parameter read tool with no output schema and no annotations, the description covers inputs, outputs, and a conditional output branch, which is close to what an agent needs to call it correctly. Remaining gaps are failure modes and data freshness, which are minor for a stats tool.

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 baseline would be 3, but the description adds real meaning: 'daily log returns' fixes the computation basis, and the explicit 30/90/180 window set is an implicit enum the schema does not enforce (window_days is typed as a bare number). It also clarifies that BTC inclusion is what enables the beta output.

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?

States a specific computation (Pearson correlation of daily log returns) over a specific universe (2-8 major crypto assets) and window (30/90/180 days), plus the derived outputs. It is clearly distinguishable from snapshot-style siblings like volatility_snapshot, though it never names or contrasts an alternative tool 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 closing clause 'Useful for diversification checks and pair selection' implies the intended use case but gives no when-to-use/when-not-to-use rules and no guidance on choosing this over volatility_snapshot or market_regime_snapshot. The 2-8 symbol bounds are the only constraint conveyed.

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