Skip to main content
Glama
0xsl1m

cerebrus-pulse-mcp

by 0xsl1m
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

cerebrus_sentiment

Obtain aggregated crypto market sentiment analysis including fear/greed, momentum, and funding bias. Pay $0.01 USDC via x402 micropayments.

Instructions

Get aggregated crypto market sentiment analysis. Returns overall sentiment, fear/greed, momentum, and funding bias. Not coin-specific. Cost: $0.01 USDC via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/cerebrus_pulse_mcp/server.py:138-149 (registration)
    Registration of the cerebrus_sentiment tool in the list_tools() function with schema and description.
    Tool(
    name="cerebrus_sentiment",
    description=(
        "Get aggregated crypto market sentiment analysis. "
        "Returns overall sentiment, fear/greed, momentum, and funding bias. "
        "Not coin-specific. Cost: $0.01 USDC via x402."
    ),
    inputSchema={
        "type": "object",
        "properties": {},
    },
),
  • src/cerebrus_pulse_mcp/server.py:383-384 (handler)
    Handler logic for the cerebrus_sentiment tool: calls the /sentiment API endpoint via _api_get().
    elif name == "cerebrus_sentiment":
    result = _api_get("/sentiment")
  • src/cerebrus_pulse_mcp/server.py:469-469 (helper)
    CLI helper mapping for the sentiment tool, defining the API path and empty parameter specs.
    "sentiment":     ("/sentiment",         []),

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Discloses cost ($0.01 USDC via x402), which is valuable behavioral info. No annotations exist, so description carries burden. Does not mention auth or rate limits, but cost is a key trait.

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 sentences, each earning its place: first defines purpose, second adds essential cost detail. No extra words.

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?

With zero parameters and no output schema, the description thoroughly explains the tool's output and constraints. Complete for expected usage.

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 has 0 parameters (100% coverage), baseline 3. Description adds context on return values and cost, exceeding baseline by providing additional meaning.

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 verb 'Get' and resource 'aggregated crypto market sentiment analysis', and specifies what is returned. It distinguishes from siblings by explicitly noting 'Not coin-specific'.

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?

Provides context on when to use by stating 'Not coin-specific', implying use for overall sentiment. Lacks explicit alternatives or when-not-to-use, but sibling names offer differentiation.

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