Skip to main content
Glama

Market-Wide 13F Activity

GetMarketWide13FActivity
Read-only

Get the market-wide 13F leaderboards for a given quarter — which stocks were most bought, most sold, most initiated, or most exited across all 13F filers vs the prior quarter. The bucket argument selects one of: top-buys (Δ shares > 0 ranked by Δ value desc), top-sells (Δ shares < 0 ranked by Δ value asc), new-positions (stocks ranked by count of filers initiating a position), sold-out-positions (stocks ranked by count of filers exiting). Every board counts only filers with a 13F in both quarters. Δ Value is the change in published position value: values normally use report-date closing prices, may fall back to filer values, and can be zero when unavailable. It includes price movement on held shares, so use Δ Shares to read the position change itself. The output publishes the first complete 13F report quarter and refuses comparisons that cross that corpus boundary. Use this to answer 'what's the consensus 13F move this quarter?' Shares and value count common shares only.

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": {
      "bucket": "<bucket>"
    },
    "name": "GetMarketWide13FActivity"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketYesBucket: top-buys, top-sells, new-positions, or sold-out-positions
maxResultsNoMaximum number of stocks to return (default: 20, clamped to 1-500)
reportDateNoQuarter-end 13F report date in YYYY-MM-DD format, e.g. 2026-03-31 (defaults to the latest available 13F quarter; an off-quarter date snaps to the nearest report on or before it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already establish this as a safe read, and the description adds substantial behavior beyond them: a corpus boundary that causes refusals for cross-boundary comparisons, the both-quarters filer requirement, the Δ Value price-movement caveat with the advice to prefer Δ Shares, and the common-shares-only scope. That is exactly the kind of caveat an agent needs before calling.

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 bucket enumeration are front-loaded, and nearly every clause carries semantic weight (ranking rules, Δ Value caveats, corpus boundary). It is dense in a single paragraph rather than clearly segmented, which costs a little readability but not a lot of waste.

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 moderately complex ranked-list tool with no output schema, the description covers eligibility, ranking logic, and value caveats well. It does not describe the shape of the returned leaderboard rows (which fields per stock), leaving a modest gap an agent must discover from the response.

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 baseline would be 3, but the description goes further by defining what each bucket value means and how each board is ranked (Δ shares sign, Δ value ordering, filer counts for initiations/exits). That adds real meaning the bare enum strings in the schema do not convey.

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 names a specific verb and resource — market-wide 13F leaderboards for a quarter — and enumerates the four buckets the tool returns. The 'across all 13F filers' scoping implicitly distinguishes it from institution-level siblings like GetInstitutionQuarterlyActivity, though it never names an alternative explicitly.

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 gives a clear use case ('what's the consensus 13F move this quarter?') and states an important eligibility constraint: only filers with 13F reports in both quarters are counted. It stops short of explicit when-not guidance or pointing to the institution-level alternative for single-filer questions.

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.