Skip to main content
Glama
stockbit-mcp

stockbit-mcp

One sector classification node

company_classification
Read-onlyIdempotent

Fetches one Stockbit sector classification node by ID, returning its direct child categories and company totals so you can map industry groups and holdings.

Instructions

One node of the sector classification (id from company_classifications) with its direct children and how many companies each holds (total_company).

The node's own name, level and total_company sit beside data; data lists the children.

Returns (Stockbit's data field): {name, symbol, level, parent_id, total_company, data[{id, name, level, parent_id, symbol, total_company}]} (the node's own fields sit beside data, not inside it)

Endpoint: GET exodus /emitten/classification.

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": {
      "id": "<id>"
    },
    "name": "company_classification"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesClassification node id, from list_classifications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot express: the exact return layout and the non-obvious fact that the node's own fields sit beside 'data' rather than nested inside it, plus the underlying endpoint. It says nothing about depth limits or whether children are one level only, which is the main behavioral unknown for a hierarchical read.

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 purpose, then the return shape, then the endpoint — a sensible order. It loses a point for redundancy: the 'own fields sit beside data, not inside it' point is made twice, once in the opening paragraph and again in a parenthetical after the Returns block.

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 correctly carries the full burden of documenting the response, and it does so field-by-field with the nesting caveat. Remaining gaps are minor: no statement on whether 'data' is one level deep or recursive, and no note on error behavior for an invalid id.

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% and the sole parameter already carries a description pointing to the source of the id, so the schema does the heavy lifting. The description's '(id from company_classifications)' adds a little provenance, but it is stated inconsistently against the schema's 'from list_classifications', leaving the agent to reconcile two different source tools.

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 the resource precisely ('one node of the sector classification') and its payload shape ('direct children and how many companies each holds'), which is concrete enough for an agent to distinguish it from a flat listing tool. It stops short of explicitly contrasting itself with siblings such as company_by_classification, but the verb+resource pairing 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 Guidelines3/5

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

Usage is only implied: the parenthetical '(id from company_classifications)' signals this is a drill-down step after listing classifications, which is helpful routing. There is no explicit when-to-use/when-not-to-use statement and no guidance on choosing between this and the sibling company_by_classification tools.

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