Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Insider / major holder transactions

ownership_insider_transactions
Read-onlyIdempotent

Track insider and major holder (above 5%) buys and sells per symbol or market-wide, returning dates, prices, and shares before/after to reveal ownership changes.

Instructions

Buys and sells reported by insiders and major holders (above 5%), per symbol or market-wide, with date, price, shares before/after.

Returns (Stockbit's data field): data{movement[{id, name, symbol, date, action_type, nationality ('NATIONALITY_TYPE_LOCAL'|'NATIONALITY_TYPE_FOREIGN'), badges[] (SHAREHOLDER_BADGE_DIREKTUR|KOMISARIS|PENGENDALI), previous{value,percentage}, current{value,percentage}, changes{value,percentage,formatted_value}, price, price_formatted, purpose, broker_detail, data_source{type}}], is_more}. Pagination: next page while is_more.

Paywall: unknown.

Endpoint: GET exodus /insider/company/majorholder.

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": "ownership_insider_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page Default 1.
limitNoPage size Default 20.
symbolNoLegacy single-symbol form used by the older Insider widget
insiderNoLegacy: insider id filter
symbolsNoRepeated key (symbols=A&symbols=B); empty = all stocks (insider-activity MF)
date_endNoYYYY-MM-DD; UI default today
date_startNoYYYY-MM-DD; UI default today-30d
action_typeNoTransaction kind Default "ACTION_TYPE_UNSPECIFIED".
period_typeNoPreset range
source_typeNoData source Default "SOURCE_TYPE_UNSPECIFIED".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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, openWorld), so the description earns credit for going further: it discloses the exact return envelope, the enum vocabularies for nationality and badges, and the pagination rule ('next page while is_more'). The 'Paywall: unknown' note is a useful honesty signal, though the absence of any note on rate limits or auth keeps it from a 5.

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 opening sentence is front-loaded and does the real work; the return-field listing is dense but justified because there is no output schema. Some raw schema jargon (nested brace syntax, 'data_source{type}') reads as a pasted payload rather than curated prose, and the endpoint line is of limited value to an agent.

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 10 optional parameters, no output schema, and a complex nested response, the description is appropriately thorough: it compensates for the missing output schema by enumerating the return shape and pagination. The main remaining gap is that action_type and period_type semantics are unspecified in both schema and description.

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 every parameter already carries its own documentation and the baseline of 3 applies. The description adds only marginal parameter meaning — the symbol-vs-market-wide distinction and the presence of a date window — and does not clarify action_type or period_type values, which remain opaque strings with no enums.

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 specific verb and resource: buys and sells reported by insiders and major holders (>5%), with explicit scope options 'per symbol or market-wide'. This clearly distinguishes a transaction-flow feed from holdings-oriented siblings such as ownership_insider_holdings, without the agent needing to open a schema.

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 implies usage through its scope statement ('per symbol or market-wide') and its filter vocabulary (date, price, shares), so an agent can infer this is the transaction-history lookup. However, it never says when to prefer it over a holdings or composition sibling, and offers no exclusions or prerequisites.

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