Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Stream posts of a symbol

stream_symbol
Read-onlyIdempotent

Fetches Stockbit community posts, news, reports, and IDX announcements for a stock symbol by category, with cursor-based pagination for browsing the symbol’s stream.

Instructions

Posts in the Stockbit stream of one symbol: community posts, news, reports and IDX announcements (category). Page with last_stream_id.

Returns (Stockbit's data field): data{stream[{stream_id, title, title_url, content, content_original, created_at, created_display, updated_at, user{user_id, username, fullname, avatar, is_verified, is_pro, user_privilege, country, verified_status}, status{is_pinned, is_trending, is_liked, is_saved, ...}, total_replies, total_likes, type, images[], polling[], attachment[], news_feed{source,label,img}, target_price[], topics[], mask_html[{mask,tag,text,attr{data_company,...}}], reports[], research, summary, reaction, parent_stream_id, reply_to}], pagination{is_last_page, next_cursor, total}, invalid_watchlist_ids[]}. Stop when is_last_page or next_cursor==0.

Endpoint: GET exodus /stream/v3/symbol/{symbol}.

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": {
      "symbol": "<symbol>",
      "category": "<category>"
    },
    "name": "stream_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDate filter (omitted when empty)
fromNoDate filter (omitted when empty)
limitNolimit Default 20.
symbolYesTicker (cleanupValue applied)
keywordNoOmitted when empty
categoryYesFeed filter (stock page tabs All/News/Reports/Ideas/...) Default "STREAM_CATEGORY_ALL".
last_replyNoSecondary cursor (omitted unless set)
report_typeNoSent with STREAM_CATEGORY_REPORTS (HAR) - default REPORT_TYPE_ALL Default "REPORT_TYPE_ALL".
last_stream_idNoCursor; 0 for first page, then pagination.next_cursor Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower, yet the description still adds real operational detail: paging is cursor-based via last_stream_id, iteration should stop at is_last_page or next_cursor==0, and report_type is only meaningful with the REPORTS category. It does not cover rate limits or auth, which keeps it out of the top band.

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

Conciseness3/5

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

The purpose sentence and paging rule are front-loaded and earn their place, but the middle is a long raw field dump (mask_html with nested attr, reaction, reply_to, trailing '...') that is low-signal and padded rather than explanatory. Structure is reasonable; economy is not.

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, the return-value enumeration is genuinely load-bearing and the stop condition plus endpoint give an agent everything needed to page correctly. Only the absence of any auth/permission or failure-mode note keeps it from being fully complete for an open-world network 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 coverage is 100%, so most parameter meaning is already documented; the description only reinforces category semantics and cursor paging, largely echoing the schema's own 'Default 0' and 'Sent with STREAM_CATEGORY_REPORTS' notes. Baseline 3 applies when the schema carries the weight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: streaming community posts, news, reports and IDX announcements for a single ticker, plus the underlying endpoint (GET exodus /stream/v3/symbol/{symbol}). That is clearly more precise than the generic title, but it never contrasts itself with the visible siblings (stream_pinned, stream_research), so an agent must still infer which stream tool to pick.

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?

Usage is implied rather than stated: the category tabs (All/News/Reports/Ideas) and the 'Page with last_stream_id' note tell the agent how to shape a call, but there is no explicit 'use this when…' and no mention of when to prefer stream_pinned or stream_research instead.

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

Deploy Server

Other Tools