Skip to main content
Glama
SEC EDGAR MCP

SEC EDGAR MCP

by reblickulous

fetch_filing

Retrieve and read cleaned text from a specific SEC filing using its CIK, accession number, and primary document, so you can review filing content.

Instructions

Fetch and read the text content of a specific SEC filing. Use the cik, accession_number, and primary_document values returned by search_filings. Returns cleaned, readable text (HTML tags stripped). Long documents are truncated — ask for a specific section if needed.

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": {
      "cik": "<cik>",
      "accession_number": "<accession_number>",
      "primary_document": "<primary_document>"
    },
    "name": "fetch_filing"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesCompany CIK number
accession_numberYesAccession number from search_filings (e.g. '0001318605-23-000012')
primary_documentYesPrimary document filename from search_filings (e.g. 'tsla-20231231.htm')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses useful details: it returns cleaned readable text with HTML tags stripped, and long documents are truncated. It does not cover error handling, permissions, or rate limits, but it discloses the key output and limitation behavior.

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 three compact sentences with no wasted wording. It front-loads the purpose, then gives the required source of parameter values, then discloses the return format and truncation behavior.

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?

For a simple three-parameter read tool with no output schema and no annotations, the description is mostly complete: it explains the input source, return format, and truncation limitation. The note to ask for a specific section is slightly ambiguous because no section parameter exists, but the core behavior is sufficiently specified.

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%, so the parameter descriptions already explain the meaning of cik, accession_number, and primary_document, including examples. The tool description reinforces that these values come from search_filings, but adds little per-parameter meaning beyond the schema.

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 states a specific verb and resource: fetch and read the text content of a specific SEC filing. It also links the tool to search_filings by requiring values returned from that tool, which distinguishes it from search-oriented siblings.

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 clearly explains that the required cik, accession_number, and primary_document values should come from search_filings, giving the agent a concrete workflow context. It does not explicitly state when not to use the tool or contrast it with get_financials and lookup_company, but the intended usage is clear.

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