Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Holdings of an investor (monthly)

ownership_investor_holdings
Read-onlyIdempotent

Retrieve every company an investor holds above 1% from monthly reports, optionally for a specific date, using the investor ID to inspect holdings and changes.

Instructions

Every company one investor holds above 1%, from the monthly report (investor id from other ownership tools).

Returns (Stockbit's data field): data{id, name, type{raw}, location{raw}, domicile, nationality, classification, report_date, grand_total, first_available_date, last_available_date, holdings[{company{id, symbol, name, icon_url}, shareholding{percentage, total_shares}, previous_shareholding, change}]}

Paywall: unknown.

Endpoint: GET exodus /insider/shareholding/investors/{investorId}.

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": {
      "investorId": "<investorId>"
    },
    "name": "ownership_investor_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
investorIdYesInvestor id (holders[].investor.id or search/v2 insiders[].id)
report_dateNoYYYY-MM-DD end-of-month; omit for latest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, openWorld. The description adds real value beyond them: the 1% inclusion threshold, the monthly-report provenance, the 'Paywall: unknown' caveat, the raw endpoint, and the full return field layout (which matters because no output schema exists). It stops short of stating pagination behavior or the effect of an invalid/unknown investorId.

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?

Front-loaded with the scope-defining sentence, then a compact return-shape block that is justified by the absence of an output schema. The trailing 'Paywall: unknown' and 'Endpoint:' lines are terse and useful for debugging, though the endpoint line is marginal for an agent caller.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the definition supplies what the agent otherwise could not know: the return payload structure, the 1% inclusion floor, month-based reporting, and the paywall uncertainty. Nothing essential to calling it correctly is missing.

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%: investorId sources and report_date's 'YYYY-MM-DD end-of-month; omit for latest' are already documented in the schema. The description adds only the 1% threshold context, which is a behavior rule rather than parameter semantics, so the baseline 3 applies.

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 with scope: 'Every company one investor holds above 1%, from the monthly report.' The 1% threshold and monthly cadence distinguish it from a generic holdings list. However, it never names the sibling distinctions (e.g. ownership_insider_holdings, ownership_investor_ubo), so differentiation must be inferred.

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?

Provides a sourcing hint for the required parameter ('investor id from other ownership tools'), which implies the caller should first use a search/holders tool. There is no explicit statement of when to use this versus insider holdings or UBO tools, and no when-not guidance, so usage is only implied.

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