Skip to main content
Glama

A 13F manager's portfolio

institutional_holdings
Read-onlyIdempotent

Read the portfolio an investment manager reported on SEC Form 13F for one quarter, largest reported value first: issuer and class as the manager wrote them, the company the security resolves to when an SEC filing ties them together (null otherwise, never guessed), shares, market value, the prior quarter's shares and the change. data.filings carries the filing with the manager's own summary totals and whether the loaded table adds up to them; data.periods lists the quarters on file. Pass holder as cik:, or pass a manager name: one match returns its portfolio, several return the matching managers with their CIKs so you can pick. Use it when asked what a manager owns, or what it bought and sold in a quarter.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 50,
      "holder": "cik:1067983"
    },
    "name": "institutional_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoKnowledge date or timestamp (YYYY-MM-DD or RFC 3339). The answer is what FinancialMD knew at that instant: only facts whose known interval contains as_of. Omit for the current view.
limitNoMaximum number of periods or items to return (default 100, at most 1000).
cursorNoOpaque cursor from a previous page (data.next_cursor).
holderYesThe manager: "cik:<n>" or a bare SEC CIK, or part of the manager's name as filed, such as "Berkshire Hathaway".
periodNoOptional calendar quarter end (YYYY-03-31, -06-30, -09-30 or -12-31). Default: the newest quarter on file.

Output Schema

NameRequiredDescriptionDefault
dataNoFor one manager: { holder: { cik, name }, period, periods, filings: [{ accession, form, report_period, filed, amendment_type, source_url, entry_total, value_total, totals_match }], items: [position], next_cursor }. For a name with several matches: { items: [{ cik, name, latest }], next_cursor }.
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent, closed-world), so the description is free to add semantics: sorting by largest reported value, the null-never-guessed resolution rule, and the filing's summary totals plus a reconciliation check against the loaded table. It does not mention rate limits, caching, or whether the reconciliation tolerance is exposed, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core content is front-loaded, but the first sentence is a long comma-spliced field enumeration that is hard to parse, and the data.filings / data.periods sentences are dense. Every clause is substantive, yet the delivery trades readability for compactness.

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?

An output schema exists, so the description need not restate return shapes, and it instead explains the envelope keys (data.filings, data.periods, data.next_cursor implied by cursor param) and the resolution null rule. What remains thin is the period default interaction with as_of (point-in-time vs. newest quarter on file), which an agent may need when combining both.

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% and each parameter is documented in-schema, but the description still adds real meaning: the holder accepted forms ('cik:<n>' or a manager name) and the disambiguation behaviour on ambiguous names, which the schema only hints at via an example. The as_of, limit, cursor and period parameters are left entirely to the schema, which is acceptable at full coverage.

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?

The description names a specific verb (read) and resource (the 13F portfolio a manager reported for one quarter), and enumerates the returned fields: issuer/class as filed, resolved company, shares, market value, prior-quarter shares and change. It also separates the data.filings and data.periods side channels, which distinguishes it from sibling list-style tools such as filings_list.

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 states the trigger clearly — 'Use it when asked what a manager owns, or what it bought and sold in a quarter' — and explains the holder-resolution branch (CIK vs. name, one match vs. several). It does not explicitly exclude or route to sibling tools like fund_holdings or institutional_holders, so an agent must infer the fund-vs-manager distinction.

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