Skip to main content
Glama
MakAcp

SEC EDGAR MCP Server

by MakAcp

edgar_filing

Retrieve and examine any SEC filing. Returns structured context with key data, extracted financials, and next steps based on company and form type or accession number.

Instructions

Use this to examine any SEC filing. Returns structured context: what the filing is, key data, and available next steps. If the filing has a typed data object (10-K, 10-Q, 8-K, Form 4, 13F, DEF 14A, etc.), returns extracted financials, sections, ownership, transactions, etc.

Two ways to specify the filing:

  1. By company + form type: identifier="AAPL", form="10-K" (gets the latest)

  2. By accession number or URL: input="0000320193-23-000077"

Examples:

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formNoForm type (10-K, 10-Q, 8-K, DEF 14A, 4, 13F-HR, etc.). Used with 'identifier'.
inputNoAccession number or URL containing an accession number (alternative to identifier+form)
detailNoDetail level for context output (default: standard)standard
identifierNoCompany ticker (AAPL), CIK (320193), or name. Used with 'form' to get the latest filing.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes the tool's functionality and return types, but does not disclose behavioral traits like authentication needs, rate limits, or error handling for invalid inputs.

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?

The description is well-organised with bullet points and examples, making it easy to read. While slightly lengthy due to examples, it remains efficient and front-loaded with purpose.

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 adequately covers the tool's purpose, parameter usage, and typical return content. It lacks mention of error responses or edge cases, but is otherwise complete.

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 description coverage is 100%, but the description adds value beyond the schema by explaining parameter combinations, the detail parameter's effect, and providing concrete examples.

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?

The description clearly states the tool examines any SEC filing and returns structured context. It provides examples and mentions key data types, but does not explicitly differentiate from sibling tools like edgar_read.

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?

The description details two ways to specify a filing with examples, offering clear context on parameter usage. However, it does not specify when not to use this tool or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MakAcp/sec-insight-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server