Skip to main content
Glama

CrowdWisdom Trading

Crowd sentiment today

get_crowd_sentiment_today
Read-onlyIdempotent

Today's crowd sentiment for one US stock or ETF from CrowdWisdom Trading: one score from -100 (all bearish) to +100 (all bullish), combining what traders say on YouTube, X, StockTwits, Reddit, brokers, podcasts and newsletters, plus how many traders it is based on. Use when the user asks about sentiment, the crowd's or retail traders' mood, or whether traders are bullish or bearish on a ticker today.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_crowd_sentiment_today"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesUS stock or ETF ticker symbol, e.g. NVDA, TSLA, SPY. Use the symbol, not the company name.

Output Schema

NameRequiredDescriptionDefault
dateNo
linkYes
moodNo
foundYes
periodYes
sourceYes
tickerYes
tradersNo
low_coverageNo
crowd_sentiment_scoreNo-100 (all bearish) to +100 (all bullish)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful context beyond that: the -100 to +100 scale, the set of sources aggregated, and that a trader-count is included. However, with an output schema present it need not restate return shape, and there is no disclosure of coverage gaps (e.g., how fresh or sparse the data might be).

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?

Two tight sentences, front-loaded with the scope and scale, then usage conditions. The enumeration of sources is informative rather than padding, though it makes the first sentence long.

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?

For a one-parameter read-only lookup with an output schema and full annotations, the description supplies everything an agent needs: the scale, the source basis, and when to invoke it. Nothing material is missing.

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 coverage is 100% for the single ticker parameter, including the 'use the symbol, not the company name' caveat. The description adds nothing about the parameter beyond what the schema already documents, 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?

States a specific verb and resource ('Today's crowd sentiment for one US stock or ETF'), the data source, and the exact scale returned (-100 to +100). Combined with 'today' versus the sibling get_crowd_sentiment_week, an agent can distinguish the two without opening either 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?

Explicit when-to-use clause covering sentiment questions, crowd/retail mood, and bullish/bearish judgments on a ticker today. It does not name the weekly sibling as the alternative for non-today ranges or state exclusions, so guidance is clear but not complete.

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.

Resources