Skip to main content
Glama

Silicon Floor

by com.siliconfloor
OverviewDiscussionsAdmin

Holdings of an investor, fund or person

get_holders
Read-only

Returns what investors hold in the tracked AI and semiconductor companies, from SEC filings. With holder — a key, a name such as 'Vanguard' or 'BlackRock', or the holder value returned by get_ownership, get_insider_trading or get_fund_flows — one holder in detail. For a fund or a company: positions by company (shares, value, weight, share of the company, move since the previous quarter, heldSince), sectors, flows, Schedule 13D/G declarations, history (what it declared every quarter since the end of 2019), performance (the return of the AI-stock portfolio it declared at the start of each quarter, held unchanged, with its rank among active managers) and follow (its page and an Atom feed of its filings). For a person: each stake broken down (breakdown: shares held and how, restricted shares, options and other rights, as the filings state them) with their roles and Forms 3, 4 and 5. Without holder, a list (list): the largest institutional holders (default), tracked companies that invest in others, the largest buyers or sellers, Schedule 13D/G holders without a 13F, individuals, or active managers ranked by the return of their declared AI-stock portfolio over period against SMH; with the sector rotation. Use it when the user asks what a fund, an investor or a person owns, or which managers bought, sold or performed most. A person can have two figures for one company — the shares held (Form 4) and beneficial ownership (Schedule 13D/G, which adds options exercisable within 60 days and unvested shares that vote): say which one is quoted. performance measures declared picks, not a fund's return. coverage.complete false means the figures are a floor.

Input Schema

NameRequiredDescriptionDefault
listNoWithout `holder`: 'largest' (default), 'investors' (universe companies filing 13F), 'buyers' or 'sellers' (by net move), 'declarants' (Schedule 13D/G holders filing no 13F), 'individuals' (people, from their 13D/G), 'performance' (active managers ranked by the return of their declared AI-stock portfolio).
limitNoRows to return (default 25, max 100).
orderNoWith list 'performance': 'best' (default: highest return first) or 'worst' (lowest first).
holderNoFor one holder's detail: its key from a list (vanguard, blackrock, nvidia), a name ('BlackRock', 'Vanguard', or a person's name), or the `holder` value another tool returned (for a director, their name and a ticker, e.g. 'Larry Ellison (ORCL)').
periodNoWith list 'performance': 'quarter' (default: the last completed quarter), 'year', '3y' or '5y' — quarterly returns chained.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / holder / description
      Previous value: -"For one holder's detail: its key from a list (vanguard, blackrock, nvidia, elon-r-musk), a name ('BlackRock', 'Elon Musk', 'Jensen Huang') or a director's SEC CIK (as get_ownership returns it)."New value: +"For one holder's detail: its key from a list (vanguard, blackrock, nvidia), a name ('BlackRock', 'Vanguard', or a person's name), or the `holder` value another tool returned (for a director, their name and a ticker, e.g. 'Larry Ellison (ORCL)')."
    • changedInput schema / properties / order / description
      Previous value: -"With list 'performance': 'best' (default) or 'worst'."New value: +"With list 'performance': 'best' (default: highest return first) or 'worst' (lowest first)."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly, non-destructive, closed-world), the description discloses genuine caveats: `coverage.complete` false means figures are a floor, `performance` measures declared picks rather than a fund's return, and a person can have two divergent figures for one company (Form 4 shares vs Schedule 13D/G beneficial ownership) that must be disambiguated. These are non-obvious data-quality warnings an agent could not infer from annotations.

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?

Purpose is front-loaded, but the explanatory block is one enormous, comma-spliced sentence whose clauses (heldSince, history, performance, follow, breakdown) are hard to scan. The volume is defensible for a five-parameter multi-mode tool, but the structure is dense enough to impede rapid parsing.

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 description must carry the return-value burden, and it does: it enumerates the fields returned in each mode (positions with shares/value/weight, sectors, flows, 13D/G declarations, history since 2019, performance with rank, follow/Atom feed, person breakdown). Nothing an agent needs to interpret results 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 still adds meaning: it spells out the accepted `holder` forms (key, company name, person name plus ticker such as 'Larry Ellison (ORCL)') and what each `list` mode returns. It goes beyond restating the schema, though the schema already covers most of this ground.

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?

The opening sentence gives a specific verb and resource ('Returns what investors hold in the tracked AI and semiconductor companies, from SEC filings') and immediately splits the behavior into the with-`holder` and without-`holder` modes. It names sibling tools (get_ownership, get_insider_trading, get_fund_flows) as key sources, so an agent can place it in the toolset without opening a 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?

It states clearly when to use it: 'Use it when the user asks what a fund, an investor or a person owns, or which managers bought, sold or performed most,' and describes the conditions that select each mode. It stops short of explicit when-not guidance or a direct alternative ('use get_ownership instead when...'), so it earns a 4 rather than a 5.

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

All Silicon Floor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources