Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Shareholder composition

ownership_composition
Read-onlyIdempotent

Retrieve a stock's ownership composition over time by investor type, including local/foreign, institutional, and retail holdings from KSEI data for a given IDX ticker.

Instructions

Ownership composition of one symbol over time by investor type (local/foreign, institution, retail …) from KSEI data.

Returns (Stockbit's data field): data{first_available_date, last_available_date, periods[{report_date, total_shares{formatted}, total_scripless{formatted}, scrip_percentage{raw,formatted}, scripless_percentage{raw,formatted}, compositions[{label, percentage{raw}, previous_percentage{raw}, shares{raw,formatted}, colors{light,dark}}]}]}

Paywall: unknown.

Endpoint: GET exodus /insider/shareholding/composition/companies/{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": "ownership_composition"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoview Default "SHAREHOLDERS_COMPOSITION_VIEW_ALL".
symbolYesIDX ticker, e.g. BBCA
period_endNoYYYY-MM-DD last day of month
period_startNoYYYY-MM-DD first day of month; omitted on first load (latest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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 externally. The description adds the upstream source (KSEI) and, importantly, the full response shape since no output schema exists — genuinely useful behavioral detail. However, it discloses nothing about paywall status (explicitly 'unknown'), rate limits, or data freshness beyond first_available_date/last_available_date field names.

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 the return contract, paywall note and endpoint in a predictable order. The return block is a dense single line and 'Paywall: unknown' is low-value, but overall there is little wasted text.

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, documenting the nested period/composition response is exactly what an agent needs, and the description does that. What is missing is selection guidance versus the many sibling ownership tools and any caveat about the undocumented 'view' parameter's alternative values.

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%, so all four parameters (symbol, view, period_start, period_end) are already documented, including the default view value and 'omitted on first load (latest)' behavior. The description adds no parameter-level semantics beyond implying a time range. Baseline 3 applies when the schema carries the burden.

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 resource and scope: 'Ownership composition of one symbol over time by investor type (local/foreign, institution, retail …) from KSEI data.' That tells an agent exactly what data comes back and its granularity. It does not explicitly differentiate from near-neighbours such as ownership_shareholders_monthly or ownership_insider_holdings, so it falls short of 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative among the ownership_* siblings. The only contextual notes are 'Paywall: unknown' and the raw endpoint path, which do not help an agent choose between tools. The implicit 'over time' framing is the only hint about appropriate use.

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