Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Research reports

stream_research
Read-onlyIdempotent

Fetch Stockbit research articles, optionally filtered by ticker symbol or keyword, and page through results using a cursor.

Instructions

Stockbit research articles, optionally for one symbol or keyword.

Returns (Stockbit's data field): data[] research items (each has id used as cursor; other fields rendered by StreamPostTimeLine - unknown). Empty array ends paging.

Paywall: unknown (research is commonly a Pro feature; no client gate found).

Endpoint: GET exodus /research.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stream_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoTicker; '' for global research feed Default "".
keywordNoText filter Default "".
last_idNoCursor: id of the last item of the previous page; 0 for first page Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. Beyond that, the description discloses the return envelope (a data[] array of research items with id usable as a cursor), states that an empty array ends paging, and flags that paywall status is unknown — real behavioral context that the annotations do not carry.

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?

The main capability is front-loaded in the first sentence, followed by the return and paging behavior in short bullet-like lines, with no filler. The trailing endpoint note (GET exodus /research) and the repeated 'unknown' hedges add little for an agent deciding how to call the tool.

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?

There is no output schema, and the description compensates by describing the return envelope, the cursor mechanism, and the paging-stop condition. It does not describe page size or result ordering, but for a simple read-only listing that is a minor omission.

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 all three parameters are already documented with types, bounds, defaults and cursor meaning. The description adds only a loose mapping back to the symbol/keyword filter and a mention that ids double as cursors, which is largely a restatement of the schema's last_id description.

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 states a specific verb and resource: listing Stockbit research articles, optionally narrowed by a symbol or keyword. That distinguishes it from account/alert siblings and from stream_pinned, though it never explicitly contrasts itself with stream_symbol, which a reader might guess is a similar feed.

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 only implied: the optional symbol/keyword phrasing tells the agent that filtering is possible, and the paging-termination rule tells it when to stop. There is no statement of when to pick this over a sibling feed and no explicit exclusion, so an agent must infer the choice from the name and the filter semantics.

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