Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

by io.github.findimitrov
OverviewDiscussionsAdmin

Get 13F Holdings — Full Parsed Infotable

Get13FHoldings
Read-onlyIdempotent
    Fetch and parse the complete equity holdings table from a specific SEC 13F-HR
    filing. Any institution managing more than $100M in US equities must file
    quarterly — this reveals their exact portfolio positions.

    Returns one record per position:
      - name_of_issuer        — company name (e.g. 'APPLE INC')
      - cusip                 — 9-character CUSIP identifier
      - title_of_class        — share class (e.g. 'COM', 'ADR')
      - value_thousands       — market value in thousands USD
      - value_usd             — market value in USD
      - shares_or_principal   — number of shares (SH) or principal amount (PRN)
      - investment_discretion — SOLE, SHARED, or OTHER
      - put_call              — 'Put' or 'Call' for options; null for equities
      - voting_sole/shared/none — voting authority breakdown

    PRIMARY USE: Step 2 of institutional holdings workflow. Obtain cik and
    accession_no from SearchEdgar13F or GetEdgarCompanyFilings, then call this
    tool to get the actual positions.

    Use min_value_thousands to filter noise (e.g. 1000 = positions ≥ $1M).
    Use sort_by='value_desc' to see the largest positions first.
    Use limit (default 100) and offset for pagination — large filers can
    have 3,000+ positions. Check _has_more in the response to know if more
    pages exist.

    Source: SEC EDGAR Archives (13F infotable XML). No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"New value: +"f258bd16-f060-4e4a-a55d-221a0484866d"
  2. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"d9f77642-e017-4785-9150-e658c2dba3a0"New value: +"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"
  3. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"New value: +"d9f77642-e017-4785-9150-e658c2dba3a0"
  4. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"3775b46a-5aa8-4586-af57-2453c8bcd08c"New value: +"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"
  5. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"d81a5175-11e9-494a-baa5-71d4ffad4ab9"New value: +"3775b46a-5aa8-4586-af57-2453c8bcd08c"
  6. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"9e7f8798-7d22-4378-b93d-179c6f8cb854"New value: +"d81a5175-11e9-494a-baa5-71d4ffad4ab9"
  7. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"9919ff85-e960-472f-863b-3de4c5abed9f"New value: +"9e7f8798-7d22-4378-b93d-179c6f8cb854"
  8. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"38452924-d5df-4668-b51c-d7cd5acabc09"New value: +"9919ff85-e960-472f-863b-3de4c5abed9f"
  9. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"fa72f604-6239-428b-81df-11f07c2c8d00"New value: +"38452924-d5df-4668-b51c-d7cd5acabc09"
  10. Changed1 schema field changed
    • changedInput schema / $defs / Holdings13FParams / properties / mcp_prompt_id / default
      Previous value: -"7b866f24-13ab-4e54-8d3a-f775612c393f"New value: +"fa72f604-6239-428b-81df-11f07c2c8d00"
  11. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark it read-only/idempotent, and the description adds meaningful extra behavior: the data source (SEC EDGAR 13F infotable XML), no-API-key requirement, one-record-per-position shape, and pagination via limit/offset with '_has_more'. This goes beyond the annotations and gives the agent realistic expectations about scale.

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

Conciseness5/5

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

The description is front-loaded with the core purpose, then uses a compact bullet list for output fields, then a brief usage sequence. Every sentence adds operational value without repeating the annotations or schema; it is long but proportional to the tool's complexity.

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?

Given output schema exists and annotations carry the safety profile, the description covers the remaining essentials: source, workflow dependency, optional filtering, pagination behavior, and the meaning of each returned field. Nothing needed to call the tool correctly appears missing.

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

Parameters5/5

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

Although schema coverage is signaled at 0%, the description compensates by explaining the important query parameters: min_value_thousands with a concrete example, sort_by='value_desc', and limit/offset with the 3,000+ position warning. It also tells the agent where to obtain cik and accession_no, tying the parameters directly to usage.

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 uses a specific verb and resource: 'Fetch and parse the complete equity holdings table from a specific SEC 13F-HR filing.' It also distinguishes itself by framing this as Step 2 after SearchEdgar13F/GetEdgarCompanyFilings and by listing exactly the return fields, so an agent can recognize it as the parsed-position tool rather than the filing-search tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides an explicit when-to-use directive: 'PRIMARY USE: Step 2 of institutional holdings workflow. Obtain cik and accession_no from SearchEdgar13F or GetEdgarCompanyFilings, then call this tool.' It also gives concrete tuning guidance for filtering, sorting, and pagination, which is more than enough to route the agent correctly.

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

All Fintel Discovery — Financial Intelligence for AI Agents 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