Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Holdings of an insider

ownership_insider_holdings
Read-onlyIdempotent

Look up an insider or major holder's ownership across companies, returning each company's symbol, name, and recent stake movements.

Instructions

What one insider or major holder owns across companies.

Returns (Stockbit's data field): data{insider_name, nationality, ownership[{symbol, company_name, recent[movement rows], is_more}]}

Paywall: unknown.

Endpoint: GET exodus /insider/majorholder/ownership.

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": {
      "insider": "<insider>"
    },
    "name": "ownership_insider_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based Default 1.
symbolNoRestrict to one company (used for 'load more' per company)
insiderYesInsider (holder) id from movement[].id
source_typeNosource_type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/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 real value beyond that: the exact return shape (insider_name, nationality, ownership array with recent movement rows and is_more), the source endpoint, and an explicit 'Paywall: unknown' caveat that an agent should know before promising data.

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 purpose sentence is front-loaded and the return shape, paywall note and endpoint follow in a compact block. Every line carries information; the terse label-value formatting ('Paywall', 'Endpoint') is efficient rather than padded.

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?

There is no output schema, but the description compensates by sketching the returned object, including the nested ownership array and the is_more pagination flag. Pagination mechanics are covered by the schema's page and symbol descriptions, so an agent has enough to invoke it correctly, with only the unresolved paywall status left open.

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 are documented in the schema itself, including page, symbol for per-company 'load more', and insider id provenance. The description adds nothing further about parameter meaning, which is acceptable at this coverage level.

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 verb and resource: what one insider or major holder owns across companies. That scope (cross-company holdings rather than a single company's shareholder list) distinguishes it from ownership siblings like ownership_insider_transactions, though it never names those siblings 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?

Usage is only implied: the insider parameter is tied to movement[].id, which hints this tool is a follow-up to a transactions lookup. There is no explicit when-to-use or when-not-to-use guidance versus ownership_insider_transactions or ownership_investor_holdings, leaving the agent to infer routing.

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