Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Structured Filing Data

get_filing_structured
Read-only

Extracts parsed, machine-readable data from SEC ownership and holdings filings by accession number, delivering structured transactions, holdings, and reporting persons for analysis.

Instructions

Parsed, machine-readable data from an ownership or holdings filing, by accession number. kind: "ownership" (Form 3/4/5 and amendments): issuer, reporting owners with relationship (director, officer title, 10% owner, or the filer's own "Other" text) and parsed.transactions (per transaction: table nonDerivative/derivative, securityTitle, transactionDate, code, acquiredDisposed A/D, shares, pricePerShare, sharesOwnedAfter, ownership D/I; derivatives add exercisePrice, exerciseDate, expirationDate, underlyingTitle, underlyingShares); "thirteen_f" (13F-HR): period, holdings with cusip, issuer, shares/principal, put/call, discretion and voting; "schedule13" (XML SCHEDULE 13D/G, 2025 onward): reporting persons, percent of class, items. 13F VALUES: valueThousands is the raw filed number, whose unit changed from thousands to whole dollars for filings on/after 2023-01-03; valueUsd / totalMarketValueUsd are normalised to dollars (null when the unit cannot be determined) and valueUnit names the unit. Holdings are capped at holdingsLimit (default 200); holdingsTotal is the full count, holdingsTruncated says whether rows were cut. A null value means not stated in the filing; it does not mean zero (a gift with no price has pricePerShare null; directShares is null on a derivative-only Form 4). parsed.transactions absent (not empty) means the table could not be read; totals still apply. parsed: null on a 13F means no information table (e.g. 13F-NT), not zero holdings. Unsupported forms, pre-2025 Schedule 13D/G and filings not in the archive return a not-found error with details.reason; their raw text remains readable as a filing document. Coverage: Signal8's SEC EDGAR archive, updated through the day, in its held range (see archiveFrom in each response; currently from late 2021, expanding back to 2016 as the history backfill fills in). Before archiveFrom it holds only a scatter, so absence before archiveFrom is not evidence a filing was never filed; SEC EDGAR itself covers earlier periods. Record-only rows (bodyStored: false) have no stored body; the document is at its sec.gov URL.

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": {
      "accessionNumber": "<accessionNumber>"
    },
    "name": "get_filing_structured"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdingsLimitNo13F only: max holdings rows to return (default 200, max 5000)
accessionNumberYesSEC accession number of a Form 3/4/5, 13F-HR or SCHEDULE 13D/G, dashed or 18-digit compact form

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish readOnly/openWorld=false/destructive=false, and the description adds substantial behavior beyond them: the 2023-01-03 13F value-unit change plus the normalised valueUsd/valueUnit fields, holdingsLimit capping with holdingsTotal and holdingsTruncated, the meaning of null versus zero, absent-vs-empty parsed.transactions, parsed:null for 13F-NT, not-found errors with details.reason, the archiveFrom coverage caveat, and record-only rows with bodyStored:false. This is exactly the non-obvious context an agent needs to avoid misreading results.

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 purpose is front-loaded and every caveat is substantive, but the body is a single dense paragraph mixing field enumerations, unit semantics, truncation, error behavior, and archive coverage, with SHOUTED labels like '13F VALUES:' and 'Coverage:' doing the structural work. It is informative but hard to scan; bullets or short labeled lines would preserve the content at much lower reading cost.

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 two-parameter read tool with an output schema, this covers everything an agent needs: which forms are supported, what each kind returns, how units and nulls behave, truncation, error cases, and archive date limits. Remaining return-value detail is delegated appropriately to the output schema.

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 baseline is 3, but the description goes further by explaining the operational effect of holdingsLimit (rows cut, holdingsTotal is the full count, holdingsTruncated flags truncation) and by asserting that a null field means 'not stated', not zero. It adds real meaning about what the single identifier unlocks rather than restating the parameter types.

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 opening sentence names a specific resource (parsed, machine-readable filing data) and the key (accession number), then enumerates the exact filing kinds covered (ownership Form 3/4/5, thirteen_f, schedule13) with the fields each returns. An agent can distinguish this from get_filing_document or search_filing_text without reading 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 Guidelines3/5

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

Usage is implied rather than stated: the description makes clear this is the structured-data path and notes that unsupported or pre-2025 forms keep their raw text 'readable as a filing document', which hints at the document-reading alternative. But it never names a sibling tool or gives an explicit when-to-use/when-not rule, so routing still requires inference.

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

Deploy Server

Other Tools