Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Pinned posts of a symbol

stream_pinned
Read-onlyIdempotent

Retrieve pinned posts for a Stockbit symbol stream, including company announcements, to surface important updates while reviewing market data.

Instructions

The posts pinned on one symbol's stream (often the company's own announcements).

Returns (Stockbit's data field): data: null when nothing pinned (HAR); otherwise stream post object(s) (same shape as stream[])

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

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>"
    },
    "name": "stream_pinned"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBCA

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, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral detail: the return is data: null when nothing is pinned, otherwise stream post object(s) matching the stream[] shape, plus the underlying endpoint. It does not mention auth or rate limits, but for a simple read that is a minor gap.

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?

Front-loaded with the purpose, then the return contract, then the endpoint — a sensible order with no filler. Minor jargon like '(HAR)' is unexplained and the endpoint line is of limited use to an agent selecting the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description supplies the key return shape including the empty case, which is the main thing missing from structured fields. It is close to complete but lacks any note on pagination, ordering, or what 'pinned' means operationally.

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?

There is a single required parameter and schema description coverage is 100%, with the schema itself giving the ticker format example (BBCA). The description only restates 'one symbol' and adds no format, casing or validation detail beyond the schema, so baseline 3 applies.

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?

States a specific resource and qualifier: the pinned posts of one symbol's stream, with the clarifying note that these are often the company's own announcements. That distinguishes it in spirit from a general stream listing like stream_symbol, though no sibling is named explicitly.

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 by the concept of 'pinned' content; there is no explicit 'use this when you want X instead of Y' or any stated prerequisite or exclusion. An agent can infer the use case but gets no routing guidance.

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