Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

aggregate_sentiment

Read-onlyIdempotent

Aggregates sentiment from Twitter/X, Reddit, Telegram, and news into unified scores, detects momentum shifts, and gauges market psychology before major moves.

Instructions

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 observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts: a per-call cost of $0.01, the momentum/trend-shift detection behavior, and the default source set. It omits weighting/aggregation methodology and any rate-limit or latency expectations, keeping it below 5.

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 core purpose is front-loaded in sentence one, then discrete labeled lines cover behavior, use case, cost, sources, and output. No sentence is filler; each labeled line carries a distinct fact an agent needs.

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?

There is no output schema, and the description compensates by describing the return (overall category plus per-source breakdown) and the numeric range, which is exactly what an agent needs. The only real gap is that it doesn't explain how conflicting source signals are resolved or how momentum is quantified, which matters for a synthesis tool.

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% and all three parameters are self-documented, so the baseline is 3. The description restates the source list, which merely mirrors the enum values in the schema, and says nothing additional about window_minutes semantics (e.g., that history is truncated at 1440 minutes) or why the default window is 60.

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 first sentence names a specific verb (aggregate) plus the resource (social media sentiment) and the scope (across multiple sources). It further distinguishes itself by naming the exact platforms and the output range (-1.0 to +1.0), so an agent can tell this apart from price/volatility siblings like analyze_volatility or fetch_price without opening the schema.

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 '**Use Case:** Gauge market psychology before major moves' line gives concrete when-to-use context, which is more than most sibling tools state. It stops short of naming when NOT to use it or pointing to an alternative (e.g., per-source vs. aggregate analysis), so it earns a 4 rather than a 5.

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