Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Trending stocks

company_trending
Read-onlyIdempotent

Fetch stocks trending on Stockbit by discussion and view activity to identify which symbols are drawing current market attention.

Instructions

Stocks trending on Stockbit right now (most discussed and viewed).

Returns (Stockbit's data field): data[{symbol, name, icon_url, trading_limit_info, day_trade_info, ...}] (prices are joined client-side from /company-price-feed/v2/orderbook)

Endpoint: GET exodus /emitten/trending.

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": "company_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely useful context absent from annotations: the response mirrors Stockbit's 'data' field, and prices are not included but joined client-side from /company-price-feed/v2/orderbook. That price-join caveat is the main value-add, but nothing is said about freshness, rate limits, or result-set size.

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?

Three short lines with the purpose front-loaded, followed by return shape and endpoint. The '(Stockbit's data field)' qualifier and the '...' ellipsis inside the field list are slightly raw, but no sentence is wasted.

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?

With no parameters and no output schema, the description carries the return-value burden and does so: it names the wrapping field, lists key member fields, and warns that prices come from a separate endpoint. An agent has everything needed to call it and interpret the result.

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

Parameters4/5

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

The tool takes zero parameters, so per the baseline this scores 4; there is no parameter semantics for the description to compensate for. The extra schema information it provides concerns the response shape rather than inputs.

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 recency scope: 'Stocks trending on Stockbit right now (most discussed and viewed)', which defines what 'trending' means operationally. It does not, however, contrast itself with the sibling market_top_stocks, so an agent must infer the distinction between trending and top-ranked lists.

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?

The 'right now' framing and the discussed/viewed definition imply when this list is appropriate, but there is no explicit when-to-use versus when-not guidance and no named alternative for top-ranked or classified stock listings. Usage is inferable rather than instructed.

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