Skip to main content
Glama

AI digest of SEC 10-K, 10-Q and 8-K filings

sec_digest
Read-only

AI-generated digest of one SEC EDGAR filing section: 10-K/10-Q risk factors (Item 1A) or MD&A, or 8-K item summaries with press-release exhibits. By accession, or ticker/CIK plus form (latest filing). Key points each carry a verbatim quote checked against the filing text and an EDGAR URL; optional new and removed risk factors versus the prior same-form filing. Generated by Anthropic Claude under a fixed Kit Rx prompt; not investment advice. Price: $0.02 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged. AI-generated answer; a call with no arguments returns the stored example answer without a model call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sec_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, 1 to 10 digits, instead of ticker.
formNo10-K, 10-Q or 8-K: required with ticker or cik (latest filing of that form).
tickerNoStock ticker (e.g. AAPL). With form, the latest filing of that form is digested.
sectionNoitem_1a (Risk Factors), item_7 (MD&A; Part I Item 2 on a 10-Q) or 8k_items. Default: item_1a for 10-K, item_7 for 10-Q, 8k_items for 8-K.
accessionNoEDGAR accession number of a 10-K, 10-Q or 8-K (e.g. 0000320193-26-000026). Alternative to ticker/cik + form.
compare_priorNo10-K/10-Q only: also read the prior filing of the same form and list new and removed risk factors (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses pricing ($0.02 per successful call, USDC x402 v2), that failed or non-matching calls are free, the generating model and prompt, quote verification against filing text, and the no-arg example path. Does not describe failure modes, rate limits, or response latency, which keeps it off a 5.

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 the core purpose and section scope, then addressing modes, then output shape, then pricing. Dense but each clause carries information; the pricing and no-arg clauses are packed into one long final sentence rather than being separated for scannability.

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?

With no output schema, the description usefully sketches the return shape (key points with verbatim quotes and EDGAR URLs, optional new/removed risk factors). For a 6-parameter, paid, AI-backed tool it is nearly complete, though it omits what a 'matched nothing' or error response looks like and any input-size or coverage limits.

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 coverage is 100%, so the schema already documents every parameter including enums and defaults. The description mostly restates those rules and only marginally adds meaning, notably that compare_prior compares against the prior same-form filing and that section defaults are form-dependent.

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 specific verb and resource — an AI-generated digest of one SEC EDGAR filing section — and enumerates exactly which sections (Item 1A risk factors, MD&A, 8-K item summaries) plus the two addressing modes (accession, or ticker/CIK + form). It is clearly differentiated from a raw-filings tool like sec_filings by the word 'digest' and the quote-verification detail.

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 concrete selection rules: accession as an alternative to ticker/cik + form, latest-filing semantics, per-form section defaults, and the notable no-argument behavior returning a stored example. It never explicitly names a sibling to use instead when raw text or a different filing view is wanted, so no exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources