Skip to main content
Glama

SEC filings batch

sec_filings_batch
Read-onlyIdempotent

Use when you need recent SEC EDGAR filings for several US public companies at once: up to 10 tickers or CIKs in one POST (duplicates removed). Returns the paid x402 request for your input (POST /sec/filings/batch, $0.03 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one company use sec_filings.

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": {
      "companies": "<companies>"
    },
    "name": "sec_filings_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNooptional, for every company: comma list of form types, e.g. 10-K,10-Q,8-K
factsNooptional, for every company: 0 = filings only (no XBRL facts; smaller response; works for big banks too), default 1 (filings plus latest facts)
limitNooptional, for every company: max filings returned (all requested forms together, newest first), as in the single call
sinceNooptional, for every company: only filings filed on/after this date, YYYY-MM-DD
companiesYes1 to 10 tickers or CIKs; duplicates are removed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / facts / description
      Previous value: -"optional, for every company: 0 = filings only (no XBRL facts; works for big banks too), default 1"New value: +"optional, for every company: 0 = filings only (no XBRL facts; smaller response; works for big banks too), default 1 (filings plus latest facts)"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world. The description adds real context beyond that: this is a paid x402 call at $0.03, it returns a request payload rather than data, and invalid input is refused before any charge — a valuable detail for cost-sensitive agents. It stops short of describing the actual returned filing payload or any rate limits.

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 when-to-use clause, then the cost and invocation mechanics, then the sibling redirect — a sensible ordering. It is dense but nearly every clause carries operational information; 'schema linked' is the one mildly opaque phrase.

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 correctly explains that the immediate return is an unconsumed x402 request body that must be POSTed to the given endpoint with an x402 or MPP client — this is the non-obvious part. It could say more about what the eventual filing data looks like, but the two-step flow and pricing are fully covered.

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 description coverage is 100%, so the schema already documents form, facts, limit, since, and companies with examples and defaults. The description only restates the 'up to 10 tickers or CIKs' bound and duplicate removal, both of which appear in the schema, adding no new parameter 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 description names a specific verb and resource (retrieve recent SEC EDGAR filings), states scope (several US public companies at once, up to 10 tickers or CIKs in one POST), and explicitly distinguishes itself from the single-company sibling sec_filings. An agent can route between the two without inspecting 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?

Opens with an explicit trigger ('Use when you need recent SEC EDGAR filings for several US public companies at once') and closes with an exclusion plus alternative ('For one company use sec_filings'). The batch-size ceiling (up to 10) and duplicate handling further constrain correct usage.

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