Skip to main content
Glama

alpha-sentinel-mcp

aggregate_sentiment

Aggregate social media sentiment across multiple sources.

Combines Twitter/X, Reddit, and other platforms into unified sentiment scores (-1.0 to +1.0). Detects momentum shifts and trend changes in community opinion.

Use Case: Gauge market psychology before major moves.

Cost: $0.01 USD per call

Sources: twitter, reddit, telegram, news

Output: Overall sentiment category (bullish/neutral/bearish) with breakdown by source.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbols": "<symbols>"
    },
    "name": "aggregate_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourcesNoData sources to query
symbolsYesList of crypto symbols to analyze
window_minutesNoTime window for sentiment history

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses per-call cost ($0.01 USD), the enumerated source set, the score normalization range, and the shape of the response. It still omits rate limits, authentication requirements, and behavior when a source is unavailable, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded and organized into scannable labeled sections (Use Case, Cost, Sources, Output), which is efficient for an agent parsing it. There is minor redundancy between the opening sentence naming Twitter/X and Reddit and the later 'Sources' line, but nothing is wasted enough to penalize heavily.

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?

With no output schema and no annotations, the description correctly compensates by describing the return values (bullish/neutral/bearish category plus per-source breakdown) and the numeric range. Cost and source coverage are covered; operational details like latency, rate limits, and partial-failure behavior are the remaining gaps for a paid aggregation call.

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?

Schema description coverage is 100%, so all three parameters are already documented in the schema. The description restates the source list and the scoring scale but adds no meaning to window_minutes (default, bounds) or to the symbols list beyond what the schema provides, so the baseline 3 applies.

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 opens with a specific verb and resource ('Aggregate social media sentiment across multiple sources') and immediately scopes it with the named platforms, the -1.0 to +1.0 score range, and the momentum-detection behavior. No sibling tool in the supplied list performs sentiment aggregation, so an agent can distinguish this immediately.

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?

The 'Use Case: Gauge market psychology before major moves' line implies when the tool is useful, but there is no explicit when-not guidance, no prerequisites, and no comparison to alternatives such as fetch_price or generate_market_report. Usage is inferable but not directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.