Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

search_sec_edgar_filings

Read-onlyIdempotent

Search SEC EDGAR corporate filings by ticker or CIK to retrieve 10-K, 10-Q, 8-K, and Form 4 documents for company research and compliance checks.

Instructions

Search official U.S. Securities and Exchange Commission (SEC) EDGAR corporate filings including 10-K annual reports, 10-Q quarterly reports, 8-K current events, and Form 4 insider transactions.

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": {
      "tickers": "<tickers>"
    },
    "name": "search_sec_edgar_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
formsNoSEC EDGAR form types to retrieve.
tickersYesPublic company stock tickers or CIK numbers (e.g., ["NVDA", "AAPL", "MSFT"]).
maxFilingsPerCompanyNoMaximum filings to return per ticker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds that the source is the official SEC EDGAR system (a meaningful authority signal), but says nothing about response latency, rate limits, or result ordering for a tool that queries an external registry by ticker.

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?

A single front-loaded sentence with the resource and scope stated first and the form-type examples trailing. No filler, though the form enumeration partially duplicates the schema enum and could be trimmed.

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?

For a read-only search tool with three fully documented parameters and annotations carrying the safety profile, the main remaining gap is that there is no output schema and the description doesn't say what a result contains (links, filing dates, text snippets) — a modest omission, not a blocking one.

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 all three parameters (tickers, forms, maxFilingsPerCompany) are already documented. The description's enumeration of form types loosely mirrors the `forms` enum and adds no new semantics such as ticker vs. CIK behavior or how results are capped.

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?

Specific verb ('Search') plus a precisely scoped resource ('official U.S. SEC EDGAR corporate filings'), with concrete examples of the form types covered (10-K, 10-Q, 8-K, Form 4). No sibling differentiation is offered, but the siblings listed are all different domains (EU tenders, FDA, literature, DeFi), so confusion is unlikely.

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?

Usage is implied by the domain — an agent can infer this is the tool for SEC filing lookups — but there is no explicit when-to-use/when-not-to-use guidance, no statement of what date range of filings is covered, and no note about when a different tool would be more appropriate.

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