Signal8 MCP Server

Official

by signal8ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Screen SEC Filings Performance

screen_sec_filings_performance

Read-only

Screen SEC filings by company and filing criteria to analyze stock price returns after filing dates, with pre-computed returns at +1, +3, +7, and +30 days and aggregate statistics.

Instructions

Analyze stock price performance after SEC filings. Returns individual filing records with pre-computed price returns at +1 day, +3 days, +7 days, and +30 days after the filing date, plus aggregate statistics (average, median, % negative, best, worst) across all matching filings. Combine company-level filters (sector, industry, market cap, exchange) with filing filters (form type, date range). Use this to answer questions like "how do biotech stocks perform after S-1 filings?" or "what is the average 7-day return after 8-K filings from companies under $500M market cap?".

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (1-indexed, default: 1)
`dateTo`	No	End date filter (YYYY-MM-DD)
`sector`	No	Filter by sector (e.g., "Healthcare", "Technology", "Financial Services")
`sortBy`	No	Sort results by field (default: filing_date)
`dateFrom`	No	Start date filter (YYYY-MM-DD)
`exchange`	No	Filter by exchange (e.g., "NASDAQ", "NYSE", "AMEX")
`industry`	No	Filter by industry (e.g., "Biotechnology", "Software - Application")
`pageSize`	No	Results per page (default: 25, max: 100)
`formTypes`	No	Comma-separated form types (e.g., "S-1", "10-K,10-Q", "8-K", "S-3,424B5")
`sortOrder`	No	Sort direction (default: desc)
`maxMarketCap`	No	Maximum market cap in USD
`minMarketCap`	No	Minimum market cap in USD

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, so no safety concern. Description adds that returns individual records with computed returns and aggregate stats. No contradictions. It could mention pagination behavior, but overall adequate.

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?

Description is a single paragraph but well-structured: purpose, outputs, filters, examples. Efficient, though could be slightly more concise. No wasted sentences.

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

Completeness5/5

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

With output schema present, description covers purpose, returns, filters, and use cases comprehensively. For a complex tool with 12 parameters, this is complete and actionable.

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 coverage is 100% with descriptions for all 12 parameters. Description adds context on filter combination and example values but does not significantly deepen understanding beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states the tool analyzes stock price performance after SEC filings, returning pre-computed returns and aggregate statistics. It distinguishes from sibling tools like get_filing_calendar or screen_sec_filings by focusing on performance analysis rather than just listing filings.

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?

Provides explicit example questions ('how do biotech stocks perform after S-1 filings?') and describes how to combine company and filing filters. However, it does not explicitly state when not to use this tool or point to alternatives like screen_sec_filings for pure filing listing.

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

Deploy Server