Skip to main content
Glama
miguelgutierrezortega5-ops

edgar-mcp-server

by miguelgutierrezortega5-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read an SEC filing

edgar_read_filing
Read-onlyIdempotent

Read SEC filing text (10-K, 10-Q, 8-K, proxies) or exhibits by company ticker, CIK, or name. Jump to sections like risk factors, locate phrases, or access press release exhibits.

Instructions

Read the text of a filing's main document (10-K, 10-Q, 8-K, proxy, S-1...) or one of its exhibits. Long documents are paginated by characters.

  • section jumps to a 10-K/10-Q section: business, risk_factors, legal_proceedings, mdna, market_risk, financial_statements.

  • find jumps to the first occurrence of a phrase (e.g. 'share repurchase', 'backlog').

  • document reads another file of the filing, e.g. the earnings press release exhibit of an 8-K ('msft-ex99_1.htm'); the header lists the filing's exhibits.

  • Otherwise continue with offset as instructed at the end of each chunk. Omit accession_number to read the latest 10-K (or 20-F/40-F).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
findNoCase-insensitive phrase to jump to.
offsetNoCharacter offset to start reading from.
companyYesCompany: US ticker ('MSFT', 'BRK.B'), SEC CIK ('789019') or company name ('Microsoft').
sectionNo10-K section to read.
documentNoFile name within the filing to read instead of the main document (see the exhibit list in the header).
max_charsNoMaximum characters to return (default 12000).
accession_numberNoAccession number from edgar_list_filings, e.g. '0001193125-26-323660'. Default: latest annual report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses pagination by characters, jump semantics, continuation via offset, and that the header lists exhibits. It also reveals that omitting accession_number returns the latest annual report. No contradiction with annotations.

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 a one-sentence core, followed by four scannable bullets that map to parameters/modes, each with concrete examples. The final sentence adds a useful default behavior. There is no filler.

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 7-parameter tool with no output schema, it covers all access modes, pagination continuation, exhibit selection, and the latest-10-K default. It also tells the agent where to find valid document filenames (the header), making the tool safely callable in realistic workflows.

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; the description adds useful semantic context with examples for find phrases, exhibit filenames, offset continuation, and accession_number default behavior. It enriches the schema without repeating it.

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 opens with a precise verb+resource: 'Read the text of a filing's main document... or one of its exhibits,' and includes the filing types covered. This clearly distinguishes it from siblings like edgar_list_filings (listing) and edgar_get_financial_statement (structured financials).

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 gives explicit operational guidance for the main modes: section, find, document, and offset continuation, and explains the default when accession_number is omitted. It does not explicitly contrast with sibling tools, but the first sentence makes the read-text use case clear.

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