Skip to main content
Glama
0xsl1m

cerebrus-pulse-mcp

cerebrus_health

Check the health status of Cerebrus Pulse gateway. No payment required for use.

Instructions

Check Cerebrus Pulse gateway health status. FREE — no payment required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool 'cerebrus_health' is registered in the list_tools() function with the name 'cerebrus_health', description 'Check Cerebrus Pulse gateway health status. FREE — no payment required.', and an empty input schema.
    Tool(
        name="cerebrus_health",
        description=(
            "Check Cerebrus Pulse gateway health status. "
            "FREE — no payment required."
        ),
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • The call_tool() handler for 'cerebrus_health' invokes _api_get('/health') to check the Cerebrus Pulse gateway health status.
    elif name == "cerebrus_health":
        result = _api_get("/health")
  • The _api_get() helper function makes the actual GET request to the Cerebrus Pulse API. It handles 402 (payment required), 429 (rate limited), and other HTTP errors, returning JSON responses.
    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()
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It states the tool checks health and is free, but does not explain what the response contains (e.g., status object, error codes), whether it requires authorization, or its reliability/availability. For a health check, typical details like response format or meaning of health indicators are missing.

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: two short sentences with zero wasted words. It front-loads the primary action and adds the free note as secondary. Every sentence adds value, and there is no redundant or extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and output schema, the description should fully explain what the tool does and what it returns. While it states the purpose, it omits critical details about the response format (e.g., status codes, JSON structure) and any other behavioral traits (e.g., latency, error handling). For a health check tool, users need to know what to expect in the output to interpret the results correctly.

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?

The tool has zero parameters, and the input schema is empty with 100% coverage. According to guidelines, a baseline of 4 is appropriate when no parameters need explanation. The description does not need to add parameter semantics, so this score reflects the minimal but adequate handling.

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: checking the health status of the Cerebrus Pulse gateway. It uses a specific verb ('Check') and resource ('Cerebrus Pulse gateway health status'), and the name 'cerebrus_health' aligns with this purpose. The tool is distinct from sibling tools, which cover other financial data endpoints.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when or why to use this tool versus its siblings (e.g., before calling other tools, or as a prerequisite). It also does not mention any context or prerequisites, such as whether authentication is needed. The only additional note is that it's free, which is a minor benefit but not usage guidance.

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