Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

sec_edgar_filings

Read-onlyIdempotent

SEC EDGAR Filings Scraper - 10-K, 10-Q, 8-K, Form 4: Real-time structured data extraction feed for SEC EDGAR Filings Scraper - 10-K, 10-Q, 8-K, Form 4.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sec_edgar_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only 'real-time structured data extraction', which does not clarify recency window, coverage scope, rate limits, or pagination behavior. It does not contradict the annotations but contributes little beyond them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The sentence is circular, repeating the title twice with the filler phrase 'Real-time structured data extraction feed for'. There is redundancy rather than front-loaded information; nothing after the colon adds value.

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

Completeness2/5

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

For a read-only, single-parameter retrieval tool with no output schema, the description should at minimum describe what a returned record contains and the recency/coverage scope. Neither is present, leaving the agent unable to predict the result shape.

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?

Only one parameter (maxResults) with 100% schema description coverage, so the schema already fully documents the input. The description adds no meaning beyond it, which matches the baseline of 3 when the schema does the work.

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

Purpose2/5

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

The description is a near-verbatim restatement of the tool name/title: 'SEC EDGAR Filings Scraper - 10-K, 10-Q, 8-K, Form 4' followed by 'extraction feed for SEC EDGAR Filings Scraper - 10-K, 10-Q, 8-K, Form 4.' The only substantive content is the list of form types, which is already in the title. It never states a concrete action (fetch latest filings? search by company? by date?).

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?

No when-to-use guidance, no exclusions, and no mention of the sibling SEC tools such as sec_13f_institutional_whale_insider_tracker that an agent must choose among. 'Real-time' hints at recency but is not framed as a selection criterion.

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