Bitget MCP — Crypto, DeFi & Macro Market Intelligence

cross_asset

Rolling cross-asset correlation: BTC vs Gold, DXY, Nasdaq, S&P500, 10Y Treasury yield, EUR/USD, oil, VIX, and any other Yahoo Finance symbol. Returns Pearson correlation (full period + rolling window) with trend and interpretation. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`base`	No	Base asset key or Yahoo Finance symbol (default: btc → BTC-USD)
`action`	Yes	correlation=compute correlation between base and targets, assets_list=list available asset keys and Yahoo symbols, heatmap=full correlation matrix for a set of assets
`assets`	No	Comma-separated assets for heatmap (default: btc,gold,dxy,ndx,spx,t10y,oil)
`period`	No	Lookback period (default: 1y)
`window`	No	Rolling window in trading days (default: 30, range: 5-252)
`targets`	No	Comma-separated target asset keys or Yahoo symbols. Default: gold,dxy,ndx,spx,t10y,vix. Use assets_list action to see available keys.

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses return values (Pearson correlation with trend and interpretation) and states 'No API key required.' No destructive behavior is expected, and no contradictions are present.

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 description is a single sentence that packs all essential information without redundancy. It could be slightly more structured, but it efficiently front-loads the purpose.

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?

Despite having no output schema, the description explains what is returned (Pearson correlation with trend and interpretation) and covers all actions and parameters. The tool has 6 parameters with 1 required, and the description is comprehensive enough for effective use.

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 description coverage is 100%, but the description adds value by explaining default values (e.g., 'base asset key or Yahoo Finance symbol (default: btc → BTC-USD)') and usage notes for actions like 'assets_list'.

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 the tool computes 'Rolling cross-asset correlation' between BTC and multiple specified assets, with the ability to use any Yahoo Finance symbol. This specific verb+resource combination distinguishes it from sibling tools like 'crypto_market' or 'global_assets'.

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 description implies usage for correlation analysis across assets and mentions no API key is required, but lacks explicit guidance on when not to use it or alternatives. Given the distinct siblings, the context is clear enough.

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

All Bitget MCP — Crypto, DeFi & Macro Market Intelligence tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0

Disambiguation3/5

Multiple tools overlap in providing crypto price data (crypto_price, crypto_market, crypto_derivatives, global_assets) and news (news_feed, tradfi_news). While descriptions clarify some differences, agents may struggle to choose between similar tools.

Naming Consistency2/5

Tool names mix styles: some are simple nouns (backtest, cn_market), others compound nouns with underscores (crypto_derivatives, derivatives_sentiment). No consistent verb_noun pattern, making it harder to infer purpose from name alone.

Tool Count3/5

With 19 tools covering a broad domain (crypto, DeFi, macro), the count feels slightly high but justifiable. However, several tools could be merged to reduce overlap and improve navigability.

Completeness4/5

The tool set covers a wide range of market intelligence needs: price data, technical analysis, sentiment, macro indicators, news, and DeFi. Minor gaps like on-chain analytics or direct trading are acceptable given the intelligence focus.

Resources

Need Help?