Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Sector classification tree

company_classifications
Read-onlyIdempotent

Fetch the IDX sector classification hierarchy from Sektor to Sub-industri, including node IDs, parent links, and English sector labels, to map companies and navigate classifications.

Instructions

The whole IDX sector classification as a tree of four levels: level 1 Sektor, 2 Sub-sektor, 3 Industri, 4 Sub-industri. Each node has an id for company_classification and company_by_classification.

Names are Indonesian; level-1 nodes carry the English sector label in symbol (e.g. "Non-Cyclical").

Returns (Stockbit's data field): data[{id, name, level (1-4), parent_id, symbol (English sector label on level 1, e.g. 'Non-Cyclical'), children[{id, name, level, parent_id, symbol, children[…]}]}]

Endpoint: GET exodus /emitten/classification/list.

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_classifications"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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, so safety needs no restating. The description instead adds behavior the annotations cannot: the tree is four levels deep, names are Indonesian while level-1 carries an English sector label in symbol, and it names the underlying data field and endpoint. It does not say whether the tree is cached/static or how large it is, which would matter for an open-world, no-parameter call.

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 resource and level scheme, then the return shape, then the endpoint. The level-1 English-symbol example appears twice (once in prose, once in the Returns line), which is mild redundancy but not harmful.

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?

There is no output schema, so the description carries the return-value burden and does it: field-by-field shape including id, name, level 1-4, parent_id, symbol, and recursive children. For a zero-parameter reference-tree tool that is sufficient to call and use it correctly.

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?

There are zero input parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not waste space inventing parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource and its exact shape: 'The whole IDX sector classification as a tree of four levels: level 1 Sektor, 2 Sub-sektor, 3 Industri, 4 Sub-industri.' It also ties the resource to the two sibling tools that consume node ids, so the agent can place it among company_classification and company_by_classification.

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?

The sentence 'Each node has an id for company_classification and company_by_classification' implicitly tells the agent this is the lookup you call first to obtain ids for the per-company tools. There is no explicit exclusion against the nearby company_sectors / company_subsectors siblings, so guidance is clear but not fully comparative.

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