Skip to main content
Glama
Sign In
edgar-mcp

edgar-mcp

by mcpwright
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_filings

Read-only

Retrieve the most recent SEC EDGAR filings for a company using its CIK, ticker, or name. Optionally filter by form type (e.g., 10-K, 8-K) and set a limit.

Instructions

List the most recent filings for one issuer, newest first.

`cik_or_query`: a CIK (digits) or a ticker/name to resolve.
`form_type`: optional prefix filter, e.g. "10-K", "8-K", "C", "D".

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": {
      "cik_or_query": "<cik_or_query>"
    },
    "name": "list_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cik_or_queryYes
form_typeNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint and openWorldHint, so description reinforces that this is a read operation. It discloses ordering and the resolution behavior for cik_or_query. However, it does not mention any rate limits, pagination, or the effect of the 'limit' parameter, which would add transparency.

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?

The description is extremely concise, with two lines of text plus parameter explanations. It is front-loaded with the main purpose and includes only essential details. Every sentence adds value.

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?

Given the tool's complexity (3 parameters, output schema exists), the description covers the main functionality and key parameters. It could improve by explaining the 'limit' parameter, but overall it is sufficient for basic usage.

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 0%, so description must compensate. It adds meaning for 'cik_or_query' (accepts digits or ticker/name) and 'form_type' (prefix filter). However, 'limit' parameter is entirely undocumented in description, leaving its purpose unclear.

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 clearly states the action ('list'), resource ('filings'), scope ('for one issuer'), and ordering ('newest first'). It distinguishes from sibling tools like 'search_filings' which likely provides more extensive search, and 'lookup_issuer' which likely finds issuer info.

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 description explains what the tool does but does not explicitly state when to use it versus alternatives. It mentions parameter usage (CIK/ticker resolution and form type filter) but lacks guidance on when not to use this tool or when to prefer 'search_filings'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools