Skip to main content
Glama
0xsl1m

cerebrus-pulse-mcp

cerebrus_correlation

Calculate 30-day rolling correlations between BTC and top 15 Hyperliquid altcoin perpetuals. Identify correlation regimes and sector averages for trading insights.

Instructions

Get BTC-altcoin correlation matrix for top 15 Hyperliquid perpetuals. Returns 30-day rolling correlations, correlation regime (CORRELATED/DECORRELATED/MIXED), and sector averages. Cost: $0.03 USDC via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for cerebrus_correlation tool — calls GET /correlation on the API with no parameters.
    elif name == "cerebrus_correlation":
        result = _api_get("/correlation")
  • Tool registration: defines 'cerebrus_correlation' in the list_tools() with description and empty inputSchema.
    Tool(
        name="cerebrus_correlation",
        description=(
            "Get BTC-altcoin correlation matrix for top 15 Hyperliquid perpetuals. "
            "Returns 30-day rolling correlations, correlation regime "
            "(CORRELATED/DECORRELATED/MIXED), and sector averages. "
            "Cost: $0.03 USDC via x402."
        ),
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Helper _api_get function used by the handler to make the actual HTTP GET request to the Cerebrus Pulse API.
    def _api_get(path: str, params: dict | None = None) -> dict[str, Any]:
        """Make a GET request to the Cerebrus Pulse API."""
        with _make_client() as client:
            resp = client.get(path, params=params)
    
            if resp.status_code == 402:
                # Return payment details so the agent/user knows cost
                return {
                    "status": "payment_required",
                    "message": "This endpoint requires x402 USDC payment on Base or Solana.",
                    "url": f"{BASE_URL}{path}",
                    "payment_details": resp.headers.get("X-Payment", "See x402 SDK docs"),
                    "help": "Install the x402 SDK and set CEREBRUS_WALLET_KEY (Base) or CEREBRUS_WALLET_KEY_SOLANA (Solana) to enable auto-payment. See https://cerebruspulse.xyz/guides/x402-payments",
                }
    
            if resp.status_code == 429:
                return {
                    "status": "rate_limited",
                    "message": "Rate limit exceeded. Back off and retry.",
                    "detail": resp.json() if resp.headers.get("content-type", "").startswith("application/json") else resp.text,
                }
    
            resp.raise_for_status()
            return resp.json()
  • CLI mapping for 'correlation' tool — maps to /correlation API path with no parameters.
    "correlation":   ("/correlation",       []),
Behavior4/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the cost ($0.03 USDC via x402), which is a key behavioral detail. The action 'Get' implies a read operation, so no destructive behavior is expected. This is sufficient.

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?

The description is a single sentence that front-loads the action and key details. Every word adds value; no redundancy.

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?

Despite having no output schema, the description lists the returned information (correlation matrix, regime, sector averages). This provides sufficient context for an agent to understand the output, though format details are missing.

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?

There are no parameters (schema coverage 100% trivially). The description adds no parameter details, but none are needed. Baseline score of 4 is appropriate.

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's purpose: getting a BTC-altcoin correlation matrix for top 15 Hyperliquid perpetuals. It specifies outputs (30-day rolling correlations, correlation regime, sector averages) and distinguishes from siblings by focusing on correlation.

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?

While the description implies usage for correlation analysis, it does not explicitly state when to use this tool versus siblings like cerebrus_basis or cerebrus_sentiment. No exclusions or alternatives are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/0xsl1m/cerebrus-pulse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server