Skip to main content
Glama

Oxford Ledge

by com.oxfordledge
OverviewDiscussionsAdmin

Institutional Holders

get_institutional_holders
Read-only

Which institutions hold one ticker, and which way they moved. Returns {ticker, holders, total_holders, as_of_quarter, coverage}. holders: the first limit (default 25, max 100) of the top 100 by value; total_holders is the TRUE filer count. Each holder carries fund_name, fund_cik, shares, value_usd (whole USD), quarter, change_type and pct_change vs that fund's prior quarter. Check coverage.basis ('universe' vs 'top_display') before quoting an aggregate. Common stock only; quarters can differ per row. Rows are CUSIP-resolved: a resolution failure drops or mis-attributes a row. Direction-only view: ol_ownership_changes; fund-keyed inverse: get_13f_holdings. Source: SEC EDGAR 13F-HR, ~45-day quarterly delay.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHolders to return from the top-100-by-value page (default 25, max 100); total_holders and coverage are unchanged.
tickerYesStock ticker symbol (e.g. AAPL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Holders to return from the top-100-by-value page (default 25, max 100); total_holders and coverage are unchanged.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation it discloses the full return shape, the true-vs-displayed holder distinction, coverage.basis semantics, common-stock-only scope, per-row quarter variance, CUSIP resolution failure behavior, and the ~45-day 13F delay. This is rich, decision-relevant behavioral context.

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-loads the purpose sentence, then organizes output fields and caveats compactly. Dense and slightly long, but nearly every clause carries actionable information.

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 13F-holdings tool with no output schema, the description carries the return-value and caveat burden well, covering structure, coverage interpretation, resolution risk, and data latency. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the limit parameter is already fully documented in the schema. The description restates the default/max and confirms total_holders and coverage are unaffected, but adds little syntax or semantics beyond what the schema already provides. Baseline 3 applies.

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 ('which institutions hold one ticker, and which way they moved') and explicitly distinguishes itself from siblings ('Direction-only view: ol_ownership_changes; fund-keyed inverse: get_13f_holdings'). An agent can route correctly without opening any 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?

Gives explicit context and names two alternatives with their differing shapes (direction-only vs fund-keyed inverse), plus a 'check coverage.basis before quoting an aggregate' precondition. Lacks a crisp when-to-use/when-not statement, but the routing is clear.

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

All Oxford Ledge 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