Regime

Diversification check

diversification_check

Read-onlyIdempotent

Diversification check: how many independent bets a basket of coins really is. Give the coins (and optionally the window: 90, 365 or 730 days): you get the average correlation between the pairs on real daily returns, the number of independent bets it works out to, each coin's correlation with bitcoin — and what the equal-weight basket did on the days bitcoin closed 3% or more down: how often it fell too, by how much, and its worst such day. Dead coins included.

Use when a basket of two or more coins is called diversified or hedged. For one coin use drawdown_check; for two or three coins side by side on every check, coin_comparison.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	Yes	Window ending on the last day of the data: 90, 365 or 730. Defaults to 365.
`coins`	Yes	Tickers or full pairs, e.g. ["BTC", "ETH", "SOL"]. A comma-separated string also works. One we do not hold comes back with the list.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	false when we do not hold that data. Never a zero standing in for an answer.
`error`	No	no_data when ok is false.
`model`	No	The assumptions, stated.
`reason`	No	Why, in one sentence, and what we do have instead.
`source`	No	The public file these numbers come from.
`btc_bad_days`	No	The days bitcoin closed 3% or more down: how many, on what share of them the basket fell too, its median and worst move. Diversification that vanishes on those days was never there.
`independent_bets`	No	N / (1 + (N-1)*avg_corr). Five coins that move as one are one bet; five that ignore each other are five.
`all_coins_we_hold`	No	What every coin we hold, at equal weights, adds up to — the ceiling, for comparison.
`correlation_with_btc`	No	Each coin's correlation with bitcoin in the window.
`average_pair_correlation`	No	Pearson correlation of daily log returns, averaged over every pair in the basket.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026
- addedInput schema / properties / days / default
```
Added value: +365
```
- addedInput schema / properties / days / enum
```
Added value: +[
+  90,
+  365,
+  730
+]
```
First observedOct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the window is optional with a default, and 'Dead coins included' tells the agent how delisted assets are handled — a meaningful data-coverage disclosure.

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?

The output set is front-loaded and the routing rule follows; every sentence carries information. It is denser than strictly necessary — the long output enumeration in sentence one could be trimmed — but nothing is wasted.

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?

With an output schema present, return values need not be explained, yet the description previews them usefully and covers the trigger, alternatives, and dead-coin handling. An agent has enough to call it correctly; only minor gaps remain.

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%, so both parameters are already documented with examples, enum values, and the missing-coin behavior. The description restates the window choices (90/365/730) without adding syntax or meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb/resource ('how many independent bets a basket of coins really is') and concretely enumerates the outputs: average pairwise correlation, independent-bet count, per-coin correlation with bitcoin, and basket behavior on bitcoin-down days. It clearly differentiates itself from siblings like drawdown_check and coin_comparison.

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

Usage Guidelines5/5

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

It explicitly names the trigger condition ('when a basket of two or more coins is called diversified or hedged') and routes to alternatives: 'For one coin use drawdown_check; for two or three coins side by side on every check, coin_comparison.' Both the when and the when-not are covered.

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

All Regime 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?