Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Shareholding network

ownership_network
Read-onlyIdempotent

Maps the ownership graph around a company or investor, showing who owns whom and shareholding percentages up to a chosen depth.

Instructions

The ownership graph around a company or investor: who owns whom, to a depth.

Returns (Stockbit's data field): data{root_id, nodes[{id, node_type, min_depth, is_rendered, metadata{company{name, symbol, icon_url} | investor{name, investor_type{raw}, location{raw}}}}], edges[{from_id, to_id, is_rendered, shareholding{percentage{raw}}}]}

Paywall: unknown.

Endpoint: GET exodus /insider/shareholding/network.

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": {
      "root_id": "<root_id>",
      "root_type": "<root_type>"
    },
    "name": "ownership_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
root_idYesCompany id or investor id
max_depthNomax_depth Default 3.
root_typeYesroot_type
max_edge_per_nodeNomax_edge_per_node Default 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description correctly spends its budget elsewhere: it documents the exact response shape (nodes, edges, shareholding percentage, min_depth, is_rendered) and flags a paywall risk. It does not cover graph size limits or truncation behavior, but the added context is substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and efficient, but the return-shape block is written as a dense raw field dump and 'Paywall: unknown.' conveys nearly nothing. Since there is no output schema, the field dump does earn its place, though it could be formatted more readably.

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 no output schema, the description carries the burden of explaining the return value and does so in detail, including node types, metadata, and edge shareholding. Missing pieces (truncation by max_edge_per_node, whether edges are directional, latency/size expectations) are minor for a read-only graph query.

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% and defaults (max_depth 3, max_edge_per_node 20) are already documented in the schema. The description only echoes 'to a depth' and the company/investor root distinction, adding little beyond what the input schema states.

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?

The description gives a specific verb+resource: 'The ownership graph around a company or investor: who owns whom, to a depth.' The notion of a traversable graph distinguishes it from list-style siblings such as ownership_shareholders_monthly or ownership_insider_holdings, but 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The only implicit signal is that the root can be a company or an investor ('around a company or investor'), plus 'to a depth' hinting at traversal use cases; an agent must infer the rest.

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