Skip to main content
Glama

FinanceQuery

SEC EDGAR Filing History

get_edgar_submissions
Read-onlyIdempotent

Get SEC filing history and company metadata from EDGAR (up to 1000 most recent filings). Requires EDGAR_EMAIL env var.

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_edgar_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum filings per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesStock ticker symbol (e.g., "AAPL", "MSFT", "TSLA")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description still adds real value beyond that: the 1000-filing cap on results and the EDGAR_EMAIL configuration requirement, which an agent cannot learn from the schema or annotations. It omits pagination behavior and any SEC rate-limit caveats, which keeps it below 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.

Conciseness5/5

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

A single front-loaded sentence with the resource named first and the two constraints (result cap, env var) trailing. No filler and nothing that could be cut without losing information.

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 four parameters at full schema coverage, rich annotations, and no output schema to explain, the description needs only scope and prerequisites. It supplies both. The remaining gap is that 'company metadata' is left unspecified and result pagination is unmentioned.

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 limit, cursor, fields, and symbol are all documented in the schema itself, making 3 the baseline. The description adds only a light contextual hint ('1000 most recent filings') that informs what limit applies to. It adds no syntax or format detail beyond the schema.

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?

States a specific verb and resource: 'Get SEC filing history and company metadata from EDGAR'. It also bounds the scope ('up to 1000 most recent filings'). It does not differentiate itself from close siblings like get_filing_sections or get_edgar_facts, so an agent must infer which EDGAR tool to use.

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

Usage Guidelines2/5

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

The description gives a prerequisite ('Requires EDGAR_EMAIL env var') but no when-to-use guidance and no named alternatives. Nothing tells the agent when to pick this over get_filing_sections (filing contents) or get_edgar_facts (structured financial facts), which is the main selection risk here.

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.