Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Screen SEC Filings

screen_sec_filings
Read-only

Screen SEC filings by form type, date range, and company filters like sector, industry, market cap, and exchange. Get enriched results with ticker, sector, industry, exchange, market cap, and price.

Instructions

Screen SEC filings across all companies with company-level filters (sector, industry, market cap, exchange) combined with filing-level filters (form type, date range). Returns filings enriched with company metadata: ticker, sector, industry, exchange, market cap, and price. Use this to answer questions like "find all S-1 filings from biotech companies under $500M market cap" or "show me recent 8-K filings from Technology sector companies". This is the most powerful filing discovery tool — use search_sec_filings only when you already know the specific CIK.

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", "Energy")
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", "Oil & Gas E&P")
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 (e.g., 500000000 for $500M)
minMarketCapNoMinimum market cap in USD (e.g., 1000000000 for $1B)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
Behavior4/5

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

Annotations already provide readOnlyHint=true. Description adds context about enriched output (ticker, sector, etc.) and mentions combining filters, but doesn't detail pagination or rate limits, which are acceptable for a read tool.

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?

Three sentences with high information density: first defines functionality, second gives examples, third provides sibling guidance. No wasted 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?

Given the tool has 12 well-described parameters, output schema, and annotations, the description covers high-level purpose, use cases, and differentiation. Nothing significant is missing.

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 baseline is 3. The description does not add extra detail beyond what the schema provides for each parameter.

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 screens SEC filings with combined company and filing filters, and provides concrete examples of questions it answers. It also distinguishes from search_sec_filings by specifying when to use each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states to use this for broad screening and search_sec_filings when CIK is known. Includes example queries to clarify use cases.

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