Skip to main content
Glama

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 Form 13F filings: the net flow of managers present at both quarters (stock pickers apart), by segment; the companies most bought and sold; the largest named moves; new big positions; full exits; and whose declared picks returned most. Default: the latest quarter past its 13F deadline; a quarter still being filed returns its first filers (wave). A 13F shows long positions at quarter end, not current holdings; method says how flows are counted. Use it when the user asks what funds bought or sold in a quarter; for one fund, get_holders; for one company, get_ownership.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fund_flows"
  }
}

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. Changed2 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +15
    • addedInput schema / properties / limit / minimum
      Added value: +1
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only annotations, it explains the 13F source, the default latest quarter past its filing deadline, and that a still-filing quarter returns first filers as a wave. It also discloses an important limitation: 13F data shows long positions at quarter end, not current holdings.

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 scope are front-loaded, and most content earns its place by covering outputs, defaults, and alternatives. However, the long semicolon-heavy listing is dense and slightly harder to scan than it could 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?

For a complex, read-only tool with no output schema, the description covers the data source, the categories returned, default quarter behavior, filing-timing caveats, and sibling alternatives. That is enough for an agent to select and invoke it correctly.

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 schema already documents limit and quarter. The description adds useful timing semantics for quarter, including default behavior and partial-quarter wave results, but the reference to `method` has no corresponding input parameter in the schema, which is a minor inconsistency.

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 and resource: returns what institutional managers did with tracked AI and semiconductor stocks in one quarter, sourced from Form 13F filings. The scope and data source are clear enough to distinguish it from generic company or holder tools.

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?

Explicitly says to use it when the user asks what funds bought or sold in a quarter, and names alternatives: get_holders for one fund and get_ownership for one company. This gives an agent concrete routing guidance rather than implied usage.

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.