Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Sub-sectors of a sector

company_subsectors
Read-onlyIdempotent

Lists sub-sectors for a given sector id or name, letting you drill from a market sector into its narrower industry groups using Stockbit data.

Instructions

The sub-sectors of one sector (use the sector id or name from company_sectors).

Returns (Stockbit's data field): data: list of subsectors (fields not consumed in the visible code; unknown)

Endpoint: GET exodus /emitten/sectors/{sector}/subsectors.

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

Input Schema

NameRequiredDescriptionDefault
sectorYesSector catalog id

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, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds the underlying endpoint (GET exodus /emitten/sectors/{sector}/subsectors) and the top-level 'data' key, but then admits the returned fields are 'unknown' and 'not consumed in the visible code', which is a developer-facing caveat rather than behavioral guidance for the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and prerequisite are front-loaded in the first sentence, which is good. The parenthetical about fields being 'not consumed in the visible code; unknown' and the raw endpoint line are internal implementation notes that consume space without helping an agent decide or invoke; trimming them would sharpen the definition.

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 does carry the burden of describing returns, and it identifies the 'data' list of subsectors and discloses that per-item fields are unknown. Combined with the prerequisite pointer and rich annotations, this is sufficient for a one-parameter lookup, though the unknown item shape leaves a small gap.

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?

Schema coverage is 100% and documents the single parameter as 'Sector catalog id', so the baseline would be 3. The description goes further by saying a sector name is also acceptable and by pointing to company_sectors as the source, which is meaning the schema alone does not convey. The slight mismatch between 'id' in the schema and 'id or name' in the description is an added detail, not a contradiction.

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?

Names the exact resource ('sub-sectors of one sector') and immediately ties it to the sibling company_sectors, which supplies the sector identifier. An agent can tell it apart from company_sectors and company_by_subsector (the inverse direction) without opening the schema. It is a noun phrase rather than a verb, but the operation is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operational context: call this with a sector id or name obtained from company_sectors, establishing a prerequisite chain. It does not state exclusions or contrast with the inverse lookup (company_by_subsector), but the usage context is explicit rather than implied.

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