Equibles

Most Widely Held Stocks

GetMostHeldStocks

Read-only

Get the cross-sectional ranking of stocks by institutional 13F breadth for a quarter. Rank by filer count (default), quarter-over-quarter filer-count change, total published position value, conviction (filers holding it among their ten largest positions) or crowding (high-turnover and private-fund adviser shares as % of shares outstanding), both among stocks 10+ filers hold. Conviction and crowding read the newest closed quarter measured across every 13F book (an open or unmeasured quarter snaps to it, noted). Values use report-date closing prices, may fall back to filer values, and can be zero when unvalued. Includes Δ filers, total value, Δ value, and share of the 13F universe. The first complete report quarter is published; earlier rankings and boundary-quarter deltas are unavailable. Only currently-held stocks rank; sold-out names use GetMarketWide13FActivity. During the newest quarter's open filing window, non-filers carry prior-quarter positions (noted in output).

Input Schema

Name	Required	Description	Default
`sort`	No	Sort by: 'filers' (default, # of 13F filers desc), 'filersDelta' (QoQ filer-count delta desc — warming names), 'filersDeltaAsc' (QoQ filer-count delta asc — cooling names), 'value' (current total published position value desc), 'conviction' (filers holding it among their ten largest positions desc) or 'crowding' (high-turnover and private-fund adviser shares as % of shares outstanding desc)	filers
`maxResults`	No	Maximum number of stocks to return (default: 25, clamped to 1-500)
`reportDate`	No	Quarter-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.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / sort / description

Previous value: -"Sort by: 'filers' (default, # of 13F filers desc), 'filersDelta' (QoQ filer-count delta desc — warming names), 'filersDeltaAsc' (QoQ filer-count delta asc — cooling names), or 'value' (current total published position value desc)"New value: +"Sort by: 'filers' (default, # of 13F filers desc), 'filersDelta' (QoQ filer-count delta desc — warming names), 'filersDeltaAsc' (QoQ filer-count delta asc — cooling names), 'value' (current total published position value desc), 'conviction' (filers holding it among their ten largest positions desc) or 'crowding' (high-turnover and private-fund adviser shares as % of shares outstanding desc)"

Changed1 schema field changedSep 3, 2026

changedInput schema / properties / sort / description

Previous value: -"Sort by: 'filers' (default, # of 13F filers desc), 'filersDelta' (QoQ filer-count delta desc — warming names), 'filersDeltaAsc' (QoQ filer-count delta asc — cooling names), or 'value' (current total reported $ value desc)"New value: +"Sort by: 'filers' (default, # of 13F filers desc), 'filersDelta' (QoQ filer-count delta desc — warming names), 'filersDeltaAsc' (QoQ filer-count delta asc — cooling names), or 'value' (current total published position value desc)"

First observedJul 19, 2026

TDQS

A4.6/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), and the description adds rich context beyond them: pricing basis (report-date closes, fallback to filer values, possible zero when unvalued), which quarter conviction/crowding read, the snapping note for open/unmeasured quarters, and non-filer carry-forward during the open filing window. These are material behaviors an agent would otherwise not know.

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?

Front-loaded with the core purpose and every sentence carries information, but the body is one dense run-on paragraph mixing edge cases, definitions, and default behavior. It earns its length but would scan faster with structure.

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, no-output-schema tool it covers the return fields (Δ filers, total value, Δ value, share of 13F universe), the ranking universe, pricing caveats, and the quarter-availability edge cases. Nothing an agent needs to call it correctly appears 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 sort/maxResults/reportDate semantics are already documented; baseline would be 3. The description adds non-obvious scope that affects interpretation of the sort options — the '10+ filers hold' universe filter and the quarter-snapping behavior — which meaningfully extends the schema.

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?

Names a specific verb and resource ('cross-sectional ranking of stocks by institutional 13F breadth for a quarter') and immediately enumerates the ranking bases. It is clearly distinguishable from siblings like GetTopHolders and GetMarketWide13FActivity, which it explicitly contrasts.

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?

Explicitly routes the agent away for one adjacent case ('sold-out names use GetMarketWide13FActivity') and states availability constraints (first complete report quarter only, earlier rankings and boundary-quarter deltas unavailable). Strong on alternatives/constraints, though it does not disambiguate against other holder-related siblings (GetTopHolders, GetHolderMix, GetInstitutionConsensusHoldings).

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

All Equibles tools Inspect

Try in Browser