Skip to main content
Glama
INo-xious

stockbit-mcp

by INo-xious

news

Read-only

Retrieve market-wide or symbol-specific headlines from Stockbit to support sentiment analysis and source discovery. Filter by keyword or date, and paginate with a cursor.

Instructions

News posts, market-wide or for one symbol. There is no separate news endpoint: news IS the stream with category=STREAM_CATEGORY_NEWS, and the Stockbit symbol page's News tab is exactly this call with a symbol. So news routes to the per-symbol stream when given a symbol and to the market-wide one when not, and fixes the category — pass stream a category instead if you want anything else. This is community- and media-written Indonesian text, not market data. Use it for sentiment and as a pointer to a source; never quote a price, a ratio or an earnings figure from a post. Headlines are Indonesian-language and mostly link out to the publisher; the link, image and publisher fields are not named by this projection, so read raw for them. from_date/to_date are YYYY-MM-DD and calendar-checked. Paging is a CURSOR, not an offset: there is no page number or offset. Take nextCursor from the result and send it as last_stream_id to get the rows AFTER the ones you have seen; calling again without it returns the same rows. nextCursor is null when the page is empty or its last row carried no id, which means the walk cannot be continued rather than that it has ended. An empty items with a non-null source is a genuine zero — a quiet symbol or a narrow keyword — and not a reason to retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows. Omitted = Stockbit's own page size.
symbolNoIDX ticker, e.g. BBRI. Omit for market-wide news.
keywordNoFull-text search over headlines and body.
to_dateNoYYYY-MM-DD, inclusive
from_dateNoYYYY-MM-DD, inclusive
last_stream_idNoCursor: the `nextCursor` from the previous page.
Behavior5/5

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

The annotations already declare readOnlyHint true and destructiveHint false, but the description adds substantial behavioral context: this is Indonesian-language community/media content, not market data; the projection drops link/image/publisher fields so `raw` must be read; date parameters are calendar-checked; and pagination is cursor-based with nuanced `nextCursor` semantics. There is no contradiction with annotations.

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 description is long but every sentence earns its place: purpose, sibling relationship, content caveats, parameter semantics, cursor pagination, and empty-result interpretation. It is front-loaded with the core purpose and routes to the correct sibling early, avoiding buried critical details.

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 tool with no output schema, the description is remarkably complete. It explains returning fields that are absent from the projection (`raw`, `source`, `nextCursor`), how to continue pagination, how to recognize a genuine zero result, and why a null cursor does not mean the stream has ended. An agent has enough context to call and interpret this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, yet the description still adds meaning beyond the schema: `symbol` presence controls per-symbol vs market-wide routing; omitting `limit` uses Stockbit's default page size; `from_date`/`to_date` are inclusive and calendar-validated; and `last_stream_id` is explicitly tied to the `nextCursor` returned from a prior page. The cursor behavior is far richer than the schema's one-line description.

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 opening line names the resource ('news posts') and the two scopes ('market-wide or for one symbol') with a concrete verb. It explicitly relates to the sibling `stream` by stating that news is the stream with STREAM_CATEGORY_NEWS, which distinguishes it from adjacent tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit routing rules: use `news` with a symbol for per-symbol news and without one for market-wide news, and direct the agent to `stream` with a custom category for anything else. It also frames appropriate usage as sentiment/pointer content and explicitly warns against quoting prices, ratios, or earnings figures from posts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/INo-xious/stockbit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server