Skip to main content
Glama

Agent Utility Suite (x402)

by io.github.vanakenj45
OverviewDiscussionsAdmin

SEC filings index and latest filings feed (free)

sec_list_filings
Read-onlyIdempotent

Free, no payment needed. Two uses: (1) with a ticker, CIK or company name, a US public company's 10-K (annual), 10-Q (quarterly) and 8-K (material event) filings from SEC EDGAR, newest first, back to 2001; (2) with no company, the latest filings across all companies from EDGAR's live feed (about the last few business days): "Which companies reported earnings since Friday?", "Who announced a CEO change today?", "Which 10-Qs were filed this morning?". Each filing has the company, ticker, form, filing date (and acceptance time in the live feed), sec.gov link, the sections sec_filing_section can extract (Risk Factors, MD&A, Business, Legal Proceedings, Market Risk, Cybersecurity) and the event items of each 8-K (earnings 2.02, executive changes 5.02, deals 1.01, cybersecurity incidents 1.05, …). Filter by form, 8-K items (codes or words like "earnings") and date. Every filing carries next_call: the exact paid tool call, with arguments and price, that returns its text. Up to 50 filings per call. Rate-limited per client.

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, e.g. 320193. Use this, `ticker` or `company`.
viaNoOptional: the tool whose next_calls suggested this call (filled in for you).
formsNoWhich filings to list: 10-K (annual), 10-Q (quarterly), 8-K (material events). Default: all three.
itemsNoOnly 8-Ks reporting any of these items, e.g. ["2.02"] for earnings, ["5.02"] for executive changes, ["1.05"] for cybersecurity incidents (words like "earnings" work too). Implies forms ["8-K"].
limitNoHow many filings to return, newest first (1-50, default 20).
sinceNoOnly filings filed on or after this date (YYYY-MM-DD). Reaches back to 2001 for one company; the market-wide feed covers about the last few business days.
tickerNoUS stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`; leave all three out for the latest filings of all companies.
companyNoCompany name, e.g. "Apple" or "Coca-Cola". Use this, `ticker` or `cik`; a name matching several companies returns their tickers, free.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / via
      Added value: +{
+  "description": "Optional: the tool whose next_calls suggested this call (filled in for you).",
+  "maxLength": 64,
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / items
      Added value: +{
+  "description": "Only 8-Ks reporting any of these items, e.g. [\"2.02\"] for earnings, [\"5.02\"] for executive changes, [\"1.05\"] for cybersecurity incidents (words like \"earnings\" work too). Implies forms [\"8-K\"].",
+  "items": {
+    "pattern": "^\\d\\.\\d{2}$",
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / properties / since / description
      Previous value: -"Only filings filed on or after this date (YYYY-MM-DD). Reaches back to 2001."New value: +"Only filings filed on or after this date (YYYY-MM-DD). Reaches back to 2001 for one company; the market-wide feed covers about the last few business days."
    • changedInput schema / properties / ticker / description
      Previous value: -"US stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`."New value: +"US stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`; leave all three out for the latest filings of all companies."
  3. Changed3 schema fields changed
    • 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`."
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses pricing ('free, no payment needed'), a per-client rate limit, a 50-filings-per-call cap, mode-dependent freshness (back to 2001 vs. the last few business days), and that every filing carries a next_call with the exact paid call, arguments and price. These are material behavioral facts an agent needs and none are in the annotations.

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 two usage modes and dense throughout; the field inventory sentence (company, ticker, form, date, link, sections, items, next_call) is efficient. The three sample questions in the live-feed mode are somewhat redundant with the prose but they illustrate the use case usefully, so nothing is wasted outright.

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 an 8-parameter, no-output-schema tool this covers the essentials: both modes, all filters, defaults and caps, freshness windows, returned fields, rate limiting, and the monetization hook. An agent can call it correctly without inferring anything significant.

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, but the description adds real meaning: items accepts words like 'earnings' and implies forms ["8-K"], a multi-company name match returns tickers for free, and since behaves differently per mode (2001 for one company, days for the market feed). It adds value over the schema text rather than 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 states a concrete verb and resource (list a company's or the market's SEC filings) and explicitly separates the two operating modes with worked example questions. It also names sec_filing_section as the tool that extracts section text, so an agent can distinguish this index/feed tool from its extraction sibling without opening a schema.

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 says when each mode applies (ticker/CIK/company = historical company filings; no company = live market-wide feed) and routes section extraction to sec_filing_section. What is missing is an explicit when-not-to-use statement or a direct comparison against siblings like sec_recent_events or sec_earnings_today, which overlap with the 'latest feed' use case.

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) toolsInspect
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