Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Subsidiaries

company_subsidiaries
Read-onlyIdempotent

Retrieve a company's subsidiaries, including ownership percentages, business types, locations, and financial details. Use it to map corporate structure and ownership exposure from a stock symbol.

Instructions

Subsidiaries of one company with ownership percentage and business.

Returns (Stockbit's data field): data{subsidiaries[{company_name, business_type, location, commercial_year, total_asset*, percentage}], last_updated_period, unit, currency}

Endpoint: GET exodus /emitten-metadata/subsidiary/{symbol}.

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": {
      "symbol": "<symbol>"
    },
    "name": "company_subsidiaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBCA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuine value beyond them by enumerating the response shape, including last_updated_period, unit, and currency, which an agent cannot get from any structured field. The unexplained asterisk on total_asset* is a small ambiguity but the return contract is otherwise well disclosed.

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?

Purpose is front-loaded in the first sentence, followed by return contract and endpoint in a compact three-block layout. Every line carries information, though the unexplained total_asset* marker slightly undercuts the precision.

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 only one simple parameter and no output schema, the description is expected to carry the return contract, and it does so in detail, including units and currency hints. What is missing is guidance on how this relates to equivalent company-overview tools, a minor gap for a simple lookup.

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% with a single required 'symbol' documented as an IDX ticker with an example, so the schema already carries the parameter meaning. The description adds nothing further about the symbol format beyond the endpoint path, making the baseline 3 appropriate.

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 first sentence names a specific resource (subsidiaries) scoped to one company and states the attributes returned (ownership percentage, business), so an agent knows exactly what it retrieves. It does not explicitly contrast itself with sibling company_* tools, which keeps it at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the many other company_* siblings, nor any prerequisites or exclusions. The only usage signal is the endpoint path implying a single-symbol lookup, which the agent must infer.

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