Skip to main content
Glama

SEC EDGAR filings (10 sats L402 or $0.01 USDC x402)

get_stock_filings
Read-only

Latest 10-K, 10-Q and 8-K filings with document links from SEC EDGAR for one US ticker. Not endorsed by the SEC. Price: 10 sats (Lightning) or $0.01 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"stock_filings","data":{"company":{"ticker":"NVDA","cik":"0001045810","name":"NVIDIA CORP"},"count":3,"forms":["8-K","10-Q","10-K"],"filings":[{"form":"8-K","filed":"2026-11-01","accession":"0001045810-26-000001","document_url":"https://www.sec.gov/Archives/edgar/data/1045810/000104581026000001/nvda-8k.htm","index_url":"https://www.sec.gov/Archives/edgar/data/1045810/000104581026000001/0001045810-26-000001-index.html"}]},"metadata":{"cost_sats":10}} Pay: Call it, get HTTP 402 (or MCP payment_required) with a Lightning invoice and macaroon, pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. Or pay in USDC on Base via x402: sign the 402's x402 requirement (PAYMENT-REQUIRED header, or accepts in the JSON body) and retry with the PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header; only a 200 is settled.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_stock_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesUS ticker. EDGAR accepts any symbol in the SEC company_tickers.json map (featured: SPY, QQQ, NVDA, TSLA, AAPL, MSFT, AMZN, META, GOOGL, AMD, AVGO, MU, PLTR, NBIS, CRWV, RKLB, INTC, ASTS, HIMS, TSM, SOFI, ORCL, HOOD, NFLX, SMCI, COIN, MSTR, IBIT, MARA, GME).
x402_paymentNoOptional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.
l402_credentialNoOptional L402 credential '<macaroon>:<preimage_hex>' (or 'L402 <macaroon>:<preimage>') from a paid invoice or an active subscription. Omit it to receive the Lightning invoice and macaroon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / x402_payment
      Added value: +{
      +  "description": "Optional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the material facts an agent cannot get elsewhere: the cost (10 sats or $0.01 USDC on Base), the two payment protocols and their exact retry headers, the fact that 'only a 200 is settled,' and a disclaimer of SEC endorsement. This is unusually complete behavioral disclosure for a paid endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is correctly front-loaded, but the body is a dense run-on of payment clauses and a large illustrative JSON blob whose field names are already implied by the schema-less response. Most of it earns its place given the dual-protocol complexity, yet the x402 sentence in particular packs three parentheticals into one breath.

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 sample response usefully reveals the return shape (company, cik, count, filings array with document_url/index_url), and the payment lifecycle is fully spelled out. What is missing is the retrieval window and result limit — the sample's count:3 hints at it but never states the default, which matters for a 'latest filings' tool.

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% and the schema itself already documents symbol scope, the x402_payment payload format, and the l402_credential format, so the baseline is 3. The description adds only the retry-header convention ('Authorization: L402 <macaroon>:<preimage>') on top of that, which is marginal new meaning.

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 opening sentence names a specific verb-scoped resource: 'Latest 10-K, 10-Q and 8-K filings with document links from SEC EDGAR for one US ticker.' That is precise enough to distinguish it from get_stock_fundamentals without opening either schema, and the illustrative sample confirms the returned fields (form, filed, accession, document_url, index_url).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Invocation guidance is strong for the payment mechanics (402 → pay invoice → retry with L402 header, or sign the x402 requirement and retry with PAYMENT-SIGNATURE/X-PAYMENT), but there is no guidance on when to pick this over a sibling such as get_stock_fundamentals, nor any statement about how many filings come back or over what window. Usage is implied by the resource description rather than stated.

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