Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Companies in a sector classification

company_by_classification
Read-onlyIdempotent

Retrieve all companies under selected classification nodes, from sector to sub-industry, with price, change, market cap, and liquidity metrics to compare peers.

Instructions

Every company under one or more classification nodes (any level: a whole sector or a single sub-industry), with price, change, market cap and liquidity. Peers at the finest grain.

One group per id in data[]. marketcap and valuema20 (20-day average traded value) are IDR; volume and avgvolume are shares.

Returns (Stockbit's data field): data[{id, level, companies[{symbol, name, company_id, last, change, percent, marketcap, valuema20, avgvolume, volume, value, followers, type_company, tradeable, company_status, notations[], uma, day_trade_info, margin_info, trading_limit_info, icon_url}], pagination{total_data}}]

Endpoint: GET exodus /emitten/classification/company.

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": {
      "ids": "<ids>"
    },
    "name": "company_by_classification"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesClassification node ids (any level); several ids give one group each.
parent_idNoParent node id, sent by the app's sector widget.
sort_orderNoOrder of the companies. TOP_LIQUIDITY sorts by valuema20 (20-day average traded value).

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?

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior. The description adds useful behavioral context beyond annotations: one group per id, unit conventions for market cap and traded value versus share volume, and the detailed return structure.

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 definition is front-loaded with purpose and then moves to units and return shape. The long return field list earns its place because there is no output schema, though the fragment 'Peers at the finest grain' and the endpoint line add marginal value.

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 description compensates well by documenting the return envelope, company fields, units, and grouping behavior. It still leaves out guidance on how to obtain classification ids, how to choose among sibling tools, and whether pagination or limits apply beyond the returned pagination total.

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 the schema already documents ids, parent_id, and sort_order. The description adds that ids may be any classification level and that multiple ids produce one group each, but it does not add direct guidance for parent_id or sort_order.

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: retrieving every company under one or more classification nodes, at any level from whole sector to single sub-industry. The scope is clear, but it does not explicitly name or differentiate itself from siblings such as company_by_subsector or company_classification.

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: call it with classification node ids, and each id returns one group. There is no explicit when-not guidance or comparison to alternative tools for sector, subsector, or classification lookup.

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