Signal8 MCP Server

Official

by signal8ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Search Filing Text

search_filing_text

Read-only

Search SEC filing exhibits for specific text clauses. Retrieve matching snippets with context, with optional filters by company, form type, or filing.

Instructions

Full-text substring search across all SEC filing exhibit content. Returns matching snippets with context around each match. Powerful for finding specific clauses like "change of control", "anti-dilution", "right of first refusal", or any specific language across filings. Optionally filter by company (CIK), filing, accession number, or form type.

Input Schema

TableJSON Schema

Name	Required	Description
`cik`	No	Filter to a specific company by CIK number
`limit`	No	Max results (default: 20, max: 100)
`pattern`	Yes	Search pattern (minimum 2 characters). Substring match, case-insensitive.
`filingId`	No	Filter to a specific filing by internal ID
`formType`	No	Filter by form type (e.g., "10-K", "S-1")
`snippetLength`	No	Characters of context around each match (default: 200)
`accessionNumber`	No	Filter to a specific filing by SEC accession number

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?

The description notes it's a substring, case-insensitive search returning snippets with context. The readOnlyHint annotation is consistent, and no contradictions exist. It could mention performance characteristics (e.g., large result sets) but is adequate.

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 (3 sentences), front-loaded with the main function, and includes practical examples and optional filter summary. No unnecessary words.

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

Completeness4/5

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

Given the presence of an output schema, the description does not need to detail return values. It covers the search scope, filters, and basic behavior. Missing details about pattern length limits (min 2 chars) but schema covers that. Overall sufficient for a read-only search tool.

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 repeats schema info for parameters (e.g., pattern is case-insensitive, optional filters) but does not add significant new semantics. Examples of search clauses provide context but don't go beyond what the schema defines.

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 performs full-text substring search across SEC filing exhibit content and returns matching snippets. It distinguishes from siblings like search_sec_filings (metadata search) and get_exhibit_content (retrieve specific content) by focusing on text search within exhibits.

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 concrete examples of use cases (e.g., finding 'change of control' clauses) and lists optional filters. While it doesn't explicitly say when not to use alternatives, the context and examples make the intended use clear.

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

Deploy Server