Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Screen SEC Filings Performance

screen_sec_filings_performance
Read-only

Analyze stock price returns after SEC filings by form type, date range, and company filters. Get pre-computed returns at 1, 3, 7, and 30 days plus 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
NameRequiredDescriptionDefault
pageNoPage number (1-indexed, default: 1)
dateToNoEnd date filter (YYYY-MM-DD)
sectorNoFilter by sector (e.g., "Healthcare", "Technology", "Financial Services")
sortByNoSort results by field (default: filing_date)
dateFromNoStart date filter (YYYY-MM-DD)
exchangeNoFilter by exchange (e.g., "NASDAQ", "NYSE", "AMEX")
industryNoFilter by industry (e.g., "Biotechnology", "Software - Application")
pageSizeNoResults per page (default: 25, max: 100)
formTypesNoComma-separated form types (e.g., "S-1", "10-K,10-Q", "8-K", "S-3,424B5")
sortOrderNoSort direction (default: desc)
maxMarketCapNoMaximum market cap in USD
minMarketCapNoMinimum market cap in USD

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
Behavior4/5

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

Annotations indicate readOnlyHint=true, and the description adds that the tool returns both individual filing records with pre-computed price returns and aggregate statistics. This goes beyond the annotation by detailing the output structure, without any contradiction.

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

Conciseness5/5

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

The description is concise with three sentences, each serving a distinct purpose: stating the function, listing filters, and providing examples. It is front-loaded and contains no unnecessary words.

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?

Despite having an output schema (as per context signals), the description covers all essential aspects: purpose, filters, and example usage. It is complete for a tool with 12 optional parameters and no required inputs.

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%, so baseline is 3. The description mentions company-level and filing filters but does not add significant meaning beyond what the schema already provides for each parameter. The examples illustrate usage but do not redefine parameter semantics.

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?

The description clearly states the tool analyzes stock price performance after SEC filings with specific return periods (+1, +3, +7, +30 days) and aggregate statistics. It distinguishes from sibling tools like screen_sec_filings by focusing on performance 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?

The description provides explicit example questions (e.g., 'how do biotech stocks perform after S-1 filings?') and explains how to combine company and filing filters. However, it does not explicitly state when not to use this tool or mention alternative tools.

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/signal8ai/signal8-mcp'

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