Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Companies in a sub-sector

company_by_subsector
Read-onlyIdempotent

List every company in a specific sub-sector with current price and change to compare peers. Use sector and subSector IDs to fetch the group.

Instructions

Every company in one sub-sector, with price and change — peers for comparison.

Returns (Stockbit's data field): data[{symbol, name, icon_url, type_company, company_status, tradeable, notations[], last, change, percent, uma, day_trade_info{multiplier}, trading_limit_info{haircut_percentage}, margin_info{percentage}, concentration{formatted}, grouping_by{type,label}, effective_date}]

Endpoint: GET exodus /emitten/v3/sector/{sector}/subsector/{subSector}/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": {
      "sector": "<sector>",
      "subSector": "<subSector>"
    },
    "name": "company_by_subsector"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYesParent catalog id. Market Overview uses the literal '70' for sector cards; special boards pass special_board[].parent_id
subSectorYesChild catalog id (pchange_info[].id or special_board[].id)

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. Beyond that, the description discloses the exact returned data fields (last, change, percent, uma, margin_info, trading_limit_info, etc.) and the underlying endpoint, which is real added context for an agent; it does not cover pagination or error behavior.

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 opening sentence is front-loaded and purposeful, and the return-field listing is justified because there is no output schema. The raw endpoint line is somewhat operational noise for an agent, keeping it out of the top score.

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 by enumerating the returned fields and their shape, and the input schema fully documents the two required ids. Missing pieces are minor: no note on result size, ordering, or empty sub-sector behavior.

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 description coverage is 100% and the schema already explains both parameters in detail, including the literal '70' sector and special_board[].parent_id cases. The description only restates the path template (sector/subsector) and adds no format or derivation guidance beyond the schema, so the 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?

The description names a specific verb and resource ('Every company in one sub-sector') and states what the result means ('peers for comparison'), which separates it from catalog-wide or classification-wide siblings. It stops short of explicitly naming a sibling it is not, so a 4 rather than a 5.

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?

'peers for comparison' implies the use case (peer lookup / comparison within a sub-sector), but there is no explicit when-to-use vs. when-not guidance and no named alternative such as company_by_catalog or company_by_classification. Usage is inferable rather than stated.

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