Skip to main content
Glama
0xsl1m

cerebrus-pulse-mcp

cerebrus_funding

Retrieve funding rate analysis for Hyperliquid perpetuals. Returns current rate, annualized percentage, and historical min/max/average for any coin ticker with adjustable lookback up to 168 hours.

Instructions

Get funding rate analysis for a Hyperliquid perpetual. Returns current rate, annualized percentage, historical min/max/average. Cost: $0.01 USDC via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesCoin ticker (e.g., BTC, ETH, SOL). Case-insensitive.
lookback_hoursNoHours of historical data (1-168). Default: 24

Implementation Reference

  • Registration and schema definition for the cerebrus_funding tool in the list_tools function. Defines the tool name, description, and input schema (coin required, lookback_hours optional with default 24).
    Tool(
        name="cerebrus_funding",
        description=(
            "Get funding rate analysis for a Hyperliquid perpetual. "
            "Returns current rate, annualized percentage, historical min/max/average. "
            "Cost: $0.01 USDC via x402."
        ),
        inputSchema={
            "type": "object",
            "properties": {
                "coin": {
                    "type": "string",
                    "description": "Coin ticker (e.g., BTC, ETH, SOL). Case-insensitive.",
                },
                "lookback_hours": {
                    "type": "integer",
                    "description": "Hours of historical data (1-168). Default: 24",
                    "default": 24,
                    "minimum": 1,
                    "maximum": 168,
                },
            },
            "required": ["coin"],
        },
    ),
  • Handler implementation in call_tool. Validates the coin, extracts optional lookback_hours (default 24), and makes a GET request to /funding/{coin} with the parameters.
    elif name == "cerebrus_funding":
        coin = _validate_coin(arguments["coin"])
        lookback = arguments.get("lookback_hours", 24)
        result = _api_get(f"/funding/{coin}", params={"lookback_hours": lookback})
  • CLI helper mapping for the funding tool, defining the API path template and parameter specs.
    "funding":       ("/funding/{coin}",    [("coin", True, str, None),
                                             ("lookback_hours", False, int, 24)]),
Behavior4/5

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

Without annotations, the description carries full transparency burden. It discloses return fields (current rate, annualized %, historical min/max/average) and cost. It does not cover auth, rate limits, or side effects, but the core behavior is clear.

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 concise sentences with no fluff. First sentence states purpose, second lists key return fields and cost. Every word adds value.

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?

Adequate for a simple tool with two parameters. Lists return fields despite no output schema. Missing details on error conditions or data freshness, but overall sufficient 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% description coverage for both parameters. The description adds the context of 'Hyperliquid perpetual,' which scopes the 'coin' parameter, but does not elaborate on parameter semantics 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 'Get funding rate analysis for a Hyperliquid perpetual,' specifying the verb (get), resource (funding rate analysis), and domain (Hyperliquid perpetual). This distinguishes it from sibling tools like cerebrus_basis or cerebrus_spread.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies Hyperliquid-specific use but does not state exclusions or prerequisites. The cost mention ($0.01 USDC) is useful but not a usage guideline per se.

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