WSB Analyst MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDDIT_CLIENT_ID | Yes | Your Reddit application client ID (appears right under 'personal use script') | |
| REDDIT_CLIENT_SECRET | Yes | Your Reddit application client secret (the string labeled 'secret') |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_top_postsB | |
| fetch_post_detailsB | |
| fetch_batch_post_detailsC | |
| fetch_detailed_wsb_postsB | |
| get_top_trending_tickersA | |
| get_external_linksB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_wsb_market | Create a prompt for analyzing WSB market sentiment and finding opportunities. |
| find_market_movers | Create a prompt for identifying what's moving a specific stock or the market. Args: ticker: Optional specific stock ticker to focus on |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
There is significant overlap between tools, particularly fetch_detailed_wsb_posts and find_top_posts which both fetch and filter WSB posts with identical parameters, causing confusion. Additionally, fetch_batch_post_details and fetch_post_details both retrieve post details, though one handles multiple IDs and the other a single ID, which could be consolidated into a single tool with an optional list parameter.
Tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., fetch_post_details, get_external_links), making them readable and predictable. However, the naming is not perfectly consistent as some tools use 'fetch' while others use 'get' for similar actions, which is a minor deviation.
With 6 tools, the count is reasonable for a server focused on WSB analysis, covering post fetching, filtering, link extraction, and ticker trending. It is slightly under-scoped as it could benefit from additional tools for deeper analysis or data manipulation, but the core functionality is adequately represented.
The toolset covers key aspects like fetching posts, extracting links, and getting trending tickers, but there are notable gaps. For example, there is no tool for updating or deleting data, and advanced features such as sentiment analysis or historical data tracking are missing, which limits comprehensive analysis workflows.