Skip to main content
Glama

SN Data by Shikshan Nivesh

Funds holding a company

get_company_fund_holders
Read-onlyIdempotent

Every fund whose latest 13F holds the company: shares, value, the stock's weight in that fund, the change from the quarter before and whether the position is new, added, trimmed, exited or held. Largest holders first. Also each quarter since June 2013: how many funds held it, their shares and the value.

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_company_fund_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
moveNoOnly funds with this move in the latest quarter, like new for funds that started a position.
limitNoMost funds to return, largest first. Default 50.
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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world behavior, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it specifies that only the latest 13F is used, that results are ordered largest first, and that quarterly history extends back to June 2013.

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 description is dense and front-loaded with the core purpose, and every clause contributes relevant information about fields, ordering, or history. It is somewhat run-on and could be split for readability, but it avoids filler.

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 return values, and it does so by naming the fund-level fields and the quarterly historical aggregates. For a three-parameter read-only lookup tool, this is nearly complete, though it could clarify how historical quarters relate to the latest-holder list.

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 the schema already explains ticker, limit, and the move enum. The description reinforces the latest-quarter scope and largest-first ordering, but adds little parameter-specific detail beyond what the schema provides, making the baseline of 3 appropriate.

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 states a specific verb and resource: it returns every fund whose latest 13F holds a given company, and it enumerates the returned fields (shares, value, weight, change, move status). It is clear what the tool does, though it does not explicitly differentiate itself from siblings such as get_large_holders or get_fund_holdings.

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 implied by the description of latest-13F holdings and the optional historical quarterly data, but there is no explicit when-to-use or when-not-to-use guidance. It does not say when an agent should prefer this over get_large_holders or get_fund_holdings, leaving that comparison to 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