Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Filing Documents

get_filing_documents
Read-only

List every document in an SEC filing by accession number, including exhibits, XBRL, and graphics, with type, size, storage status, and SEC URL.

Instructions

List every document in one SEC filing by accession number (the primary document, each exhibit, XML and XBRL files, graphics) with seq, type (e.g. "8-K", "EX-99.1"), description, size in bytes, stored and secUrl. Also returns the filing's cik, companyName, formType, filingDate, acceptedAt, bodyStored, primaryDocument, indexUrl, and filingId. A document with an exhibitId has readable stored text under that exhibit id; filingId identifies the whole submission text. exhibitId: null means the document has no readable text row here (XML/XBRL/graphics, or text not held); its secUrl still opens it. When readableIdsResolved is false the id lookup failed and exhibitId is omitted (unknown, not "none"). stored: false means Signal8 holds the filing record but not that document's body; it exists on EDGAR at secUrl. A filing not held in the archive returns a not-found error; its documents are still on EDGAR. 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_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
accessionNumberYesSEC accession number, dashed ("0001193125-22-010026") or 18-digit compact form

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare a safe read; the description adds genuinely non-obvious semantics: exhibitId null means no readable text row (not an error), exhibitId omitted means the id lookup failed and is unknown, stored: false means record-only with the body on EDGAR, and the archive coverage window is disclosed. This is exactly the failure/caveat context an agent needs before drawing conclusions from a missing row.

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?

The core scope is front-loaded in the first sentence and most of the length is substantive caveat content. However, it is a single dense paragraph, and the record-only/stored: false behavior is explained twice (once mid-paragraph, again in the closing sentence), which is avoidable repetition.

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?

An output schema exists, so field-by-field return documentation is not required, yet the description still covers the flags an agent could misread (exhibitId variants, stored, readableIdsResolved) plus archive coverage and the not-found case. Nothing needed to call this correctly or interpret its results 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?

With one parameter at 100% schema coverage, the schema already documents the dashed or 18-digit compact accession-number format, and the description only restates 'by accession number' without adding syntax constraints. Baseline 3 is correct — the schema does the work here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: 'List every document in one SEC filing by accession number', and enumerates what comes back (primary document, exhibits, XML/XBRL, graphics). It implicitly separates itself from the singular siblings by explaining the exhibitId/filingId routing, but never names get_filing_document, get_filing_exhibits, or get_exhibit_content, so sibling differentiation is inferable rather than explicit.

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 clear context for use — enumerate all documents in a known filing — plus strong boundary guidance: a filing not in the archive returns not-found, and absence before archiveFrom is explicitly not evidence a filing was never filed. It stops short of naming an alternative tool for retrieving document text or for searching when the accession number is unknown.

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