Skip to main content
Glama

SN Data by Shikshan Nivesh

Large holders (13D and 13G)

get_large_holders
Read-onlyIdempotent

13D and 13G filings and amendments, newest first: the holder, percent and shares held, the event date and the filing.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_large_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly rows on or before this date (year-month-day).
fromNoOnly rows on or after this date (year-month-day).
limitNoMost rows to return, newest first. Default 25.
tickerYesThe company's ticker, like AAPL. BRK.B and BRK-B both work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral value on top: it states the sort order (newest first) and what each row contains, effectively compensating for the absence of an output schema.

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

Conciseness5/5

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

A single dense sentence with the resource front-loaded and the payload/ordering details following. No filler, no restatement of the title, and nothing an agent would need trimmed.

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?

For a four-parameter, read-only lookup with no output schema, the description supplies the return-field list and ordering, which is the main missing piece. Minor residual gaps (pagination beyond the 500 limit, whether original and amended filings are interleaved) are small relative to how much is already covered by schema and annotations.

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 (ticker, from, to, limit) is already documented with format and defaults. The description only echoes the 'newest first' ordering tied to limit; it adds no new syntax or constraint detail, so the baseline of 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?

Names a specific resource — 13D and 13G filings and amendments — and enumerates the returned fields (holder, percent, shares, event date, filing), which clearly separates it from generic holder tools like get_company_fund_holders or get_insider_holdings. It is a noun phrase rather than a verb-led statement, so it describes content more than action, but the resource is unmistakable.

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?

There is no explicit when-to-use/when-not-to-use guidance and no sibling is named as an alternative. However, the specific regulatory form types (13D/13G) imply the use case — large/beneficial ownership stakes — strongly enough that an agent can route to it without further inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources