Agent Utility Suite (x402)

SEC 10-K / 10-Q section extractor

sec_filing_section

Read-onlyIdempotent

Answers questions like "What are Tesla's risk factors?", "What did Apple's MD&A say about margins?" or "How has Microsoft's cybersecurity disclosure changed since 2023?". Returns exactly one section of a US public company's 10-K (annual) or 10-Q (quarterly) report from SEC EDGAR as clean text, ready for an LLM: Risk Factors (Item 1A), Management's Discussion and Analysis (MD&A), Business, Legal Proceedings, Market Risk, or Cybersecurity. Look up by stock ticker or CIK. Defaults to the latest filing; pass fiscal_year (2001 on) for an earlier year's report, or accession_number for an exact filing (the free sec_list_filings tool lists them, with the sections each one has). For several sections of one filing use sec_filing_sections; for what changed since last year, sec_section_changes. The table of contents, page numbers, hidden XBRL data and HTML are removed; tables are kept as readable rows. Includes the filing date, fiscal period, accession number and sec.gov link for citation. Use it for investment research, due diligence, competitor analysis or risk monitoring without downloading a 100-page filing. Sections up to 200,000 characters. If the filing's item only points elsewhere ("See Note 12"), you get 404 SECTION_INCORPORATED_BY_REFERENCE with that pointer, free. You are only charged when a result is returned: invalid input (400) and upstream failures (4xx/5xx) are not settled. Costs $0.01 USDC per call via x402. Paid per call with x402 inside MCP (see the server instructions).

Input Schema

Name	Required	Description
`cik`	No	SEC Central Index Key, e.g. 320193. Use this, `ticker` or `company`.
`via`	No	Optional: the tool whose next_calls suggested this call (filled in for you).
`form`	No	Annual report (10-K, the default) or quarterly report (10-Q). With `accession_number`, taken from that filing.
`ticker`	No	US stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`.
`company`	No	Company name, e.g. "Apple" or "Coca-Cola". Use this, `ticker` or `cik`; a name matching several companies returns their tickers, free.
`section`	Yes	Which section to return: risk_factors, mda (Management's Discussion and Analysis), business, legal_proceedings, market_risk, or cybersecurity (10-K only, filings from late 2023 on).
`fiscal_year`	No	Return the report whose fiscal period ends in this calendar year instead of the latest one, e.g. 2022 for Apple's 10-K for the year ended September 24, 2022. For a 10-Q, the latest quarter ending in that year. EDGAR has HTML filings from 2001 on.
`accession_number`	No	Return the section from this exact 10-K or 10-Q filing of the company, e.g. 0000320193-22-000108.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / via

Added value: +{
+  "description": "Optional: the tool whose next_calls suggested this call (filled in for you).",
+  "maxLength": 64,
+  "type": "string"
+}

Changed3 schema fields changedOct 6, 2026

changedInput schema / properties / cik / description

Previous value: -"SEC Central Index Key, e.g. 320193. Use this or `ticker`."New value: +"SEC Central Index Key, e.g. 320193. Use this, `ticker` or `company`."

addedInput schema / properties / company

Added value: +{
+  "description": "Company name, e.g. \"Apple\" or \"Coca-Cola\". Use this, `ticker` or `cik`; a name matching several companies returns their tickers, free.",
+  "maxLength": 120,
+  "minLength": 2,
+  "type": "string"
+}

changedInput schema / properties / ticker / description

Previous value: -"US stock ticker, e.g. AAPL, MSFT, BRK-B. Use this or `cik`."New value: +"US stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`."

First observedOct 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), and the description layers on substantial extra behavior: TOC/page numbers/XBRL/HTML are stripped while tables are kept as rows, output carries filing date, fiscal period, accession number and sec.gov link, a 200,000-character cap, the 404 SECTION_INCORPORATED_BY_REFERENCE edge case with its free pointer, and the billing rule that only settled results are charged ($0.01 USDC via x402, 400/4xx/5xx not settled).

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?

Front-loaded with example questions and the core one-section guarantee, then routing, edge cases, and pricing in descending priority. Every sentence carries information, but the opening question examples and the citation/pricing detail make it longer than strictly necessary for an expert agent.

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?

No output schema exists, so the description must describe returns and it does: clean text with citation metadata, a character cap, and explicit error semantics for by-reference sections and invalid input. Combined with 100%-covered parameters and rich annotations, nothing an agent needs to invoke this correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description adds genuine semantics beyond the schema: lookup defaults to the latest filing, fiscal_year (2001+) selects an earlier report with 10-Q mapping to the latest quarter ending in that year, and a company-name ambiguity resolves to a free list of tickers. It stops short of restating enum syntax, which the schema already handles.

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?

States a precise verb and resource: returns exactly one section (risk_factors, mda, business, etc.) of a US public company's 10-K/10-Q from SEC EDGAR as clean text. It explicitly distinguishes itself from siblings sec_filing_sections (several sections of one filing) and sec_section_changes (year-over-year deltas), so an agent can route without opening either schema.

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?

Names the alternatives and the exact condition that selects each: sec_filing_sections for several sections, sec_section_changes for what changed, sec_list_filings to discover accession numbers. It also gives positive use cases (investment research, due diligence, competitor analysis) and states the tool's scope as a single-section extractor.

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

All Agent Utility Suite (x402) tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?