Skip to main content
Glama
0xsl1m

cerebrus-pulse-mcp

cerebrus_bundle

Retrieve combined technical analysis (5m to 1w), sentiment, and funding rates for any crypto coin in one API call, saving 20% vs individual endpoints.

Instructions

Get complete analysis bundle: multi-timeframe technical analysis (5m/15m/1h/4h/1d/1w) + sentiment + funding combined in one call. 20% discount vs individual endpoints. Cost: $0.04 USDC via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesCoin ticker (e.g., BTC, ETH, SOL). Case-insensitive.
timeframesNoComma-separated timeframes: 5m, 15m, 1h, 4h, 1d, 1w. Default: 1h,4h1h,4h

Implementation Reference

  • Tool registration for cerebrus_bundle in the list_tools() function. Defines the tool's name, description, and inputSchema (coin required, timeframes optional).
    Tool(
        name="cerebrus_bundle",
        description=(
            "Get complete analysis bundle: multi-timeframe technical analysis "
            "(5m/15m/1h/4h/1d/1w) + sentiment + funding combined in one call. "
            "20% discount vs individual endpoints. Cost: $0.04 USDC via x402."
        ),
        inputSchema={
            "type": "object",
            "properties": {
                "coin": {
                    "type": "string",
                    "description": "Coin ticker (e.g., BTC, ETH, SOL). Case-insensitive.",
                },
                "timeframes": {
                    "type": "string",
                    "description": "Comma-separated timeframes: 5m, 15m, 1h, 4h, 1d, 1w. Default: 1h,4h",
                    "default": "1h,4h",
                },
            },
            "required": ["coin"],
        },
    ),
  • Handler for cerebrus_bundle inside call_tool(). Validates the coin parameter, gets optional timeframes (default: '1h,4h'), and makes a GET request to /bundle/{coin} with those query params.
    elif name == "cerebrus_bundle":
        coin = _validate_coin(arguments["coin"])
        timeframes = arguments.get("timeframes", "1h,4h")
        result = _api_get(f"/bundle/{coin}", params={"timeframes": timeframes})
  • CLI registration for cerebrus_bundle (mapped to 'bundle') in _CLI_TOOLS, with the same path template /bundle/{coin} and params (coin required, timeframes optional with default '1h,4h').
    # ── CLI (--json mode) ───────────────────────────────────────────────────────
    
    # Maps CLI tool names to (api_path_template, param_specs).
    # param_specs: list of (name, required, type, default).
    _CLI_TOOLS: dict[str, tuple[str, list[tuple[str, bool, type, Any]]]] = {
        "list-coins":    ("/coins",             []),
        "health":        ("/health",            []),
        "pulse":         ("/pulse/{coin}",      [("coin", True, str, None),
                                                 ("timeframes", False, str, "1h,4h")]),
        "sentiment":     ("/sentiment",         []),
        "funding":       ("/funding/{coin}",    [("coin", True, str, None),
                                                 ("lookback_hours", False, int, 24)]),
        "bundle":        ("/bundle/{coin}",     [("coin", True, str, None),
                                                 ("timeframes", False, str, "1h,4h")]),
        "screener":      ("/screener",          [("top_n", False, int, 30)]),
        "oi":            ("/oi/{coin}",         [("coin", True, str, None)]),
        "spread":        ("/spread/{coin}",     [("coin", True, str, None)]),
        "correlation":   ("/correlation",       []),
        "stress":        ("/arb",              [("limit", False, int, 10)]),
        "cex-dex":       ("/cex-dex/{coin}",    [("coin", True, str, None)]),
        "basis":         ("/basis/{coin}",      [("coin", True, str, None)]),
        "depeg":         ("/depeg",             []),
        "liquidations":  ("/liquidations/{coin}", [("coin", True, str, None)]),
    }
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It discloses the cost and the fact that it's a bundled call, but does not mention authentication, rate limits, or output structure. This is adequate but not comprehensive for a complex tool.

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 extremely concise, using a single sentence and two short clauses to convey the tool's purpose, components, discount, and cost. Every word adds value, with 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?

Given the tool's complexity as a bundle of multiple analyses and the lack of an output schema, the description sufficiently covers what the tool does and its cost. It helps distinguish from many sibling tools, but could benefit from a brief note on the output format.

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?

The input schema has 100% description coverage for both parameters (coin and timeframes). The description adds only marginal value, listing timeframes already in the schema and implying no additional constraints. Thus, the description does not significantly enhance parameter understanding beyond the schema.

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 it provides a 'complete analysis bundle' combining multi-timeframe technical analysis, sentiment, and funding for a coin. It explicitly lists the timeframes and components, differentiating it from sibling tools that offer individual analyses.

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 mentions a '20% discount vs individual endpoints', implying this tool is cost-effective when needing all analyses together. However, it does not specify scenarios where the bundle would be inappropriate (e.g., if only one analysis type is needed).

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