Skip to main content
Glama

CrowdWisdom Trading

Crowd sentiment this week

get_crowd_sentiment_week
Read-onlyIdempotent

This week'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 since Monday, plus how many traders it is based on. Use when the user asks about weekly sentiment or the crowd's view for the week on a ticker.

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_week"
  }
}

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.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real substance: the -100 to +100 score scale and its endpoints, the aggregation window (since Monday), the source set (YouTube, X, StockTwits, Reddit, brokers, podcasts, newsletters), and that a trader count accompanies the score. It does not cover edge cases such as unknown tickers or coverage gaps, so it falls 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?

Two sentences with no filler, and the score semantics are front-loaded before the usage cue. The first sentence is heavily packed with clauses (scale, sources, window, sample size), which makes it dense but still scannable.

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?

For a single-parameter read tool with an output schema and full annotation coverage, the description supplies enough: what the score means, its range, its inputs, and its time window. Only failure-mode context (invalid or uncovered ticker) is missing, which is minor here.

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% and the ticker property already documents the symbol format with examples. The description only restates the universe ('one US stock or ETF'), adding no resolution rules or error behavior beyond what the schema supplies, 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 names a specific verb and resource ('crowd sentiment for one US stock or ETF') and pins the scope two ways: 'This week's' and 'since Monday'. That temporal scoping also implicitly separates it from get_crowd_sentiment_today, so an agent can pick between the two without opening a 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 positive guidance is given: 'Use when the user asks about weekly sentiment or the crowd's view for the week on a ticker.' It states the condition clearly but offers no exclusion or named alternative for the daily case, leaving that routing to the caller.

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