Skip to main content
Glama
Sign In
GMPSignal Real-Time Intelligence MCP (59 Tools)

GMPSignal Real-Time Intelligence MCP (59 Tools)

Official
by xpayrcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

sec_edgar_filings

Extract structured real-time data from SEC EDGAR filings, including 10-K, 10-Q, 8-K and Form 4 reports, with a configurable result limit.

Instructions

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 structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely fails. 'Real-time' and 'structured data extraction feed' hint at freshness and output shape, but there is no disclosure of rate limits, authentication, pagination, whether documents or only metadata are returned, or what happens when no filings match.

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 text is near-pure duplication: the title, then the same title again prefixed with 'Real-time structured data extraction feed for'. Not a single sentence front-loads useful information about inputs, outputs, or scope, so the length is wasted rather than earned.

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?

The most consequential gap is that the tool exposes only maxResults — there is no company, ticker, or CIK parameter explained anywhere, so an agent cannot tell how to scope which issuer's filings are retrieved. For a data-extraction tool with no output schema and no annotations, the description should at minimum clarify the selection mechanism and return 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?

Schema description coverage is 100% and the single parameter (maxResults) is fully documented in the schema, so the baseline of 3 applies. The description adds no meaning about what a 'structured item' is, so it neither compensates nor detracts.

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

Purpose3/5

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

The description does name concrete artifact types (10-K, 10-Q, 8-K, Form 4), so an agent knows the resource domain is SEC filings. However, the only verb is the circular 'SEC EDGAR Filings Scraper' repeated twice, so the actual action (extract? list? fetch structured records?) is inferred rather than stated. It also does nothing to distinguish this tool from the sibling sec_13f_institutional_whale_insider_tracker.

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?

There is no when-to-use guidance, no exclusions, and no mention of when a caller should prefer this over the other SEC-related sibling. Usage is only implied by the form-type list, leaving the agent to guess the selection conditions.

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