Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Monthly shareholder list (KSEI)

ownership_shareholders_monthly
Read-onlyIdempotent

Retrieve shareholders holding over 1% of a company from monthly ownership reports, including holdings and changes, by ticker and optional report month.

Instructions

The shareholders above 1% of one company from the monthly report, with holdings and changes. Takes the ticker; the tool looks up the numeric company id.

Endpoint: GET exodus /insider/shareholding/companies/{companyId}.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBCA.
report_dateNoReport month as YYYY-MM-DD; default the latest.

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, openWorld and non-destructive, so the safety profile is covered. The description adds genuine context beyond them: the 1% cutoff, the monthly reporting cadence, and the ticker-to-companyId resolution step. It says nothing about pagination, result size limits, or what 'changes' are measured against, leaving the mutation-adjacent detail thin.

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?

The data scope and threshold are front-loaded in the first sentence, followed by the invocation note. The trailing HTTP endpoint line is developer-facing noise for an agent but is short and does not obscure the main content.

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?

For a two-parameter, non-nested read tool with no output schema, the description covers what it returns (holdings plus period-over-period changes) and how the identifier is resolved. Only the exact shape of the returned rows and the treatment of the report_date default remain unstated, which is minor.

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%, with both symbol and report_date documented in the schema, so the baseline is 3. The description reinforces that symbol is a ticker and that an internal id lookup occurs, but adds no format or default detail beyond what the schema already provides for report_date.

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?

States a specific resource (shareholders holding more than 1% of a single company) and its source (the monthly KSEI report), plus what the result contains (holdings and changes). That is far more informative than the title alone and implicitly separates it from the other ownership_* tools, though no sibling is named explicitly.

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?

The description tells the agent it only needs a ticker because the numeric company id is resolved internally, which is real invocation guidance. It gives no when-to-use/when-not-to-use framing against ownership_composition or ownership_insider_holdings, so selection still requires inference.

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