Skip to main content
Glama

Silicon Floor

by com.siliconfloor
OverviewDiscussionsAdmin

Institutional buying and selling by quarter

get_fund_flows
Read-only

Returns what institutional managers did with the tracked AI and semiconductor stocks in one quarter, from their SEC Form 13F filings: filings read, managers and value declared; the net flow of managers present at both quarters (stock pickers separated from index funds, market makers and wealth platforms); net flow by segment; the companies most bought and sold (net value, share of the company, largest buyer or seller); what stock pickers bought and sold; the largest moves of named managers; new positions weighing 5% to 50% of a portfolio; positions sold in full; companies that gained or lost the most holders; and the managers whose declared AI picks returned the most over the quarter. Default: the latest quarter whose 13F deadline (45 days after quarter end) has passed; a quarter still being filed returns its first filers (wave). Use it when the user asks what hedge funds or institutions bought or sold in a quarter. Flows are share changes valued at the quarter's price, never changes in declared value; a stock listed during the quarter has no flows. A 13F shows long positions at quarter end, filed up to 45 days later, not current holdings. For one fund or person, use get_holders; for one company's shareholders, use get_ownership.

Input Schema

NameRequiredDescriptionDefault
limitNoRows per list (default 6, max 15).
quarterNo'latest' (default) or a quarter such as 'q2-2026'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds substantial domain behavior: the 45-day 13F filing deadline, what the default quarter resolves to, the 'wave' behavior for quarters still being filed, and the crucial caveat that flows are share changes valued at quarter price rather than changes in declared value.

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 purpose and routing are front-loaded, but the middle is one very long semicolon-chained sentence enumerating every returned sub-section; against the absence of an output schema this earns most of its length, yet it is denser than it needs to be.

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?

With no output schema, the description compensates by enumerating the return contents, and it supplies the default-resolution logic, filing-window semantics, and caveats an agent needs to interpret results correctly. Nothing material 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 both parameters are documented. The description still adds meaning for 'quarter' by explaining the default ('latest quarter whose 13F deadline has passed') and the wave behavior, going beyond the schema's terse enum description; it says less about 'limit'.

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 (returns) and resource (what institutional managers did with tracked AI/semiconductor stocks from SEC Form 13F filings), and distinguishes itself from siblings by explicitly naming get_holders and get_ownership as the tools for single-fund or single-company questions.

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

Usage Guidelines5/5

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

Explicit when-to-use trigger ('Use it when the user asks what hedge funds or institutions bought or sold in a quarter') plus clear routing to alternatives for one fund/person and one company's shareholders.

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