mcp

Correlation

get_correlation

Read-only

[DRILL-DOWN] Return-correlation + beta of a coin to BTC and ETH over a 7d window of 15m log returns, plus its most/least correlated peers. Descriptive statistic (correlation is not causation). Same data as REST /correlation/{coin}.

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": {
      "coin": "<coin>"
    },
    "name": "get_correlation"
  }
}

Input Schema

Name	Required	Description	Default
`coin`	Yes

Output Schema

Name	Required	Description	Default
`coin`	Yes
`to_btc`	No
`to_eth`	No
`disclaimer`	No
`most_correlated`	No
`least_correlated`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds that this is a 'Descriptive statistic (correlation is not causation)', warning against causal interpretation, and notes it mirrors REST /correlation/{coin}, which goes beyond the readOnlyHint and openWorldHint annotations. No contradiction with annotations.

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, with the main functionality in the first sentence and a caveat/reference in the second. Every element adds value; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the readOnlyHint, openWorldHint, and an output schema, the description covers the computation window, base assets, peer list, and the REST equivalent. It is sufficiently complete for an agent to understand what to expect.

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 schema lists a single required 'coin' parameter with no description, and the description only says 'of a coin' without specifying expected format (e.g., symbol vs name). With 0% schema coverage, this leaves the parameter semantics largely undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb ('Return') and resource ('correlation + beta of a coin to BTC and ETH'), along with the window and peers, which distinguishes it from sibling tools like get_prices or get_signal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The '[DRILL-DOWN]' prefix signals this tool is for detailed correlation analysis of a single coin, giving clear context. It does not explicitly mention alternatives or when to avoid it, but the unique purpose makes usage context clear.

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

All mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?