Skip to main content
Glama

Institutional holdings (13F)

akkru_institutional_holdings
Read-onlyIdempotent

What institutional managers report holding each quarter on SEC Form 13F, by manager (filer CIK) and quarter. Links open the filing's EDGAR index page.

  • managers: managers whose latest name matches query, or whose CIK is query when it is all digits; up to 8, largest latest portfolio first, with their latest quarter. 10 credits.

  • history: one manager's quarters (cik, or the exact name) with each quarter's headline numbers and its quarter label (e.g. "2026Q2", for portfolio). 30 credits.

  • portfolio: one manager's holdings for one quarter: positions, derivatives and positions closed out (exited), under a header with the quarter's numbers and its amendment record. 30 credits per page.

  • holders: who holds one security (cusip or ticker), row by row, or one row per quarter with group_by_quarter. 30 credits per page; 40 grouped.

  • search: screen every manager-quarter by its numbers (conditions), by quarter end dates and flags. Pro plan or higher; 160-720 credits. An unknown manager, quarter or security returns 404 and is still charged.

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": {
      "action": "<action>"
    },
    "name": "akkru_institutional_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNo(history, portfolio) Manager (filer) CIK, digits without leading zeros (from action "managers"). Give cik or name, not both.
nameNo(history, portfolio) Manager name, exact apart from spaces and case; a name several managers share returns 404.
pageNo(history, portfolio, holders, search) Page number, from 1; the response's next_page gives the next one.
typeNo(portfolio, holders) "positions" (stock rows), "derivatives" (option rows) or "exited" (positions closed out that quarter); default all three.
cusipNo(portfolio, holders) 9-character CUSIP. portfolio: only this security; holders: the security (or give ticker).
queryNo(managers) Manager name (1-64 characters; under 3 characters matches the start of the name) or CIK digits.
actionYesWhat to do; each action is described in the tool description.
detailNoResponse detail, same price at every level: "full" (default) returns everything; "light" leaves out the bulkiest fields, such as breakdown lists; "minimal" returns only the values and what identifies them, without sources or calculation details. Every action takes it; a call without detail levels ignores it. Try "light" or "minimal" for shorter replies that use less context and fewer tokens.
tickerNo(portfolio, holders) Security ticker; any symbol the company has traded under. portfolio: only this security; holders: the security (or give cusip).
quarterNo(portfolio, holders) Calendar quarter "YYYYQn", e.g. "2026Q1" (Q1 ends March 31, Q2 June 30, Q3 September 30, Q4 December 31). portfolio: required; holders: default every quarter.
sort_byNo(portfolio, holders, search) portfolio, holders: period, d_shares, ticker, issuer_norm or type (holders also shares or value); search: total_positions_value (default), positions_count, derivatives_count, total_derivatives_notional, portfolio_value_qoq_pct, top1_security_pct, top10_security_pct, est_turnover, period or filing_date.
activityNo(portfolio, holders) Any of "NEW", "ADD", "REDUCE", "HOLD", "CUSIP_CHANGE"; unknown values are dropped with a warning. Exited rows have no activity.
end_dateNo(search) Only quarters ending on or before this date, "YYYY-MM-DD". Omit both dates for every quarter.
restatedNo(portfolio) Any of "added", "modified", "cancelled": rows a merged amendment changed.
page_sizeNo(history, portfolio, holders, search) Rows per page, 1-100 (default 50); search: page times page_size at most 500.
conditionsNo(search) Up to 8 {field, op, value}; op is >, >=, <, <= or between ([low, high]); field is total_positions_value, positions_count, derivatives_count, total_derivatives_notional, portfolio_value_qoq_pct, top1_security_pct, top10_security_pct, est_turnover, cover_table_value, new_count, add_count, reduce_count, hold_count, sold_out_count or filing_date ("YYYY-MM-DD"). A quarter where the field is empty never matches.
is_amendedNo(search) true: only quarters with merged amendments; false: only quarters without.
sort_orderNo(history, portfolio, holders, search) "desc" (default) or "asc".
start_dateNo(search) Only quarters ending on or after this date, "YYYY-MM-DD".
confidentialNo(search) true: only quarters with confidential holdings; false: only without.
group_by_quarterNo(holders) true: one row per quarter (holders, total shares, total value of stock rows), unpaged.
is_combination_reportNo(search) true: only combination reports (the filer also reports for other managers); false: only holdings reports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent, and the description adds what they cannot: per-action credit costs (10/30/40/160-720), Pro-plan requirement for search, per-page charging, and that a 404 for an unknown manager/quarter/security is still billed. It also notes that links open the EDGAR index page and that portfolio carries the amendment record.

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 one-sentence scope followed by five tight action bullets, one line per action. Phrasing is telegraphic ('10 credits.', 'exited') but nothing is wasted.

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?

Covers all five actions, their costs, plan gating, error behavior, and paging ('30 credits per page', 'next_page' in schema), which is enough to call a 22-parameter tool correctly. Output shape is only sketched ('row by row', 'header with the quarter's numbers') and no output schema exists, but the gap is minor against the schema's per-param documentation.

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 description coverage is 100% and each parameter is already tagged with its applicable actions, so the description's action-by-action summary largely restates structured data. It adds little parameter-level detail beyond page-size implications in the credit lines.

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?

Opens with a specific verb+resource: what institutional managers report holding each quarter on SEC Form 13F, keyed by manager CIK and quarter. The five actions are each named and scoped, so an agent can tell managers/history/portfolio/holders/search apart without opening the 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?

Each action has an explicit selection rule (managers to discover CIKs, history for quarters, portfolio for one quarter, holders for reverse lookup, search for screening) plus a plan gate on search. It never names a sibling tool or states when NOT to use this instead of akkru_initial_holdings, so routing is intra-tool only.

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.

Resources