Skip to main content
Glama

SEC Accession Index (All Filings)

filings_all
Read-onlyIdempotent

Full SEC accession index per filer - every filing, all form types, newest first. (Source: SEC EDGAR filing index.)

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": {
      "rssd_id": "<rssd_id>"
    },
    "name": "filings_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description adds two genuinely useful facts beyond that — result ordering ('newest first') and provenance (SEC EDGAR filing index) — but says nothing about result volume, pagination, or rate limits, which matter for a 'full' index that could be very large.

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?

Two short sentences, front-loaded with the core scope and ordering. The parenthetical source note is marginally useful provenance rather than noise, though it could be trimmed without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the definition covers what it returns (all filings, all form types, newest first) adequately. It is incomplete on the one thing an agent needs before calling an index-wide endpoint: expected response size and whether results are paginated or truncated.

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% and the single required parameter (rssd_id) is documented as a Federal Reserve RSSD id. The description's 'per filer' loosely ties the id to a filer, but adds no syntax, format, or resolution guidance beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (full SEC accession index) and scope (per filer, every filing, all form types, newest first), which lets an agent tell it apart from filtered siblings like sec_filings by implication. It stops short of naming the alternative explicitly.

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?

The phrase 'every filing, all form types' implies this is the unfiltered/complete variant and that narrower tools exist, but no when-to-use condition or named alternative is stated. Usage is inferable rather than instructed.

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