Skip to main content
Glama
stockbit-mcp

stockbit-mcp

What an investor ultimately owns (UBO)

ownership_investor_ubo
Read-onlyIdempotent

Look up the companies an investor ultimately owns, directly or through subholdings, with current and prior-month shares, percentage, and value by investor ID.

Instructions

The companies one investor ultimately owns, directly and through holding companies (subholdings), with shares, percentage and value now and a month earlier. The investor-side view of ownership_ubo. Investor id from ownership_shareholders_monthly (holders[].investor.id).

Monthly data: first_available_date and last_available_date bound report_date. Works best for individuals; corporate investors often answer empty holdings. Values IDR.

Returns (Stockbit's data field): data{id, name, type{raw}, classification{raw ('Individual'|'Corporate')}, location, nationality, domicile, report_date, first_available_date, last_available_date, grand_total{percentage, total_shares, value, change}, holdings[{company{id, symbol, name}, shareholding{total_shares, percentage, value, price, subholdings[]}, previous_shareholding, change}]}. Corporate investors often answer empty holdings.

Endpoint: GET exodus /insider/ubo.

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": {
      "investor_id": "<investor_id>"
    },
    "name": "ownership_investor_ubo"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: monthly granularity bounded by first/last_available_date, IDR denomination, and the repeated warning that corporate investors often answer empty holdings. The empty-result caveat is the kind of trait an agent cannot infer from annotations, though the endpoint string is low-value filler.

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 core purpose, then the id source, then bounds, then return shape — a sensible order with no wasted framing sentences. It loses a point for redundancy: 'Corporate investors often answer empty holdings' appears twice in close proximity.

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?

There is no output schema, so the definition carries the return contract itself, and it enumerates the nested data/holdings/grand_total structure with field names. Combined with the IDR unit, date bounds, and the empty-holdings caveat, nothing an agent needs to call or interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it pins investor_id's provenance to a specific sibling field, and it explains that report_date is end-of-month and constrained by the returned first_available_date/last_available_date bounds rather than an arbitrary date.

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 ('the companies one investor ultimately owns, directly and through holding companies') and explicitly frames itself as 'the investor-side view of ownership_ubo', which lets an agent separate it from that sibling without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives the entry condition (you need an investor id, sourced from ownership_shareholders_monthly holders[].investor.id) and a valuable caveat that it works best for individuals while corporate investors often return empty holdings. It names the complementary tool but does not spell out an explicit 'use ownership_ubo instead when...' rule, so it falls just short of a 5.

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