Skip to main content
Glama

Signal8

by ai.signal8

Search Filing Text

search_filing_text
Read-only

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
NameRequiredDescriptionDefault
cikNoFilter to a specific company by CIK number
limitNoMax results (default: 20, max: 100)
patternYesSearch pattern (minimum 2 characters). Substring match, case-insensitive.
filingIdNoFilter to a specific filing by internal ID
formTypeNoFilter by form type (e.g., "10-K", "S-1")
snippetLengthNoCharacters of context around each match (default: 200)
accessionNumberNoFilter to a specific filing by SEC accession number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

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.

All Signal8 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Many tools have distinct purposes, but there are several groups of closely related tools (e.g., multiple insider trading and politician tools) that could cause confusion. Overall, an agent can generally distinguish tools, but the boundaries between some are fuzzy.

Naming Consistency5/5

All tool names use a consistent verb_noun pattern (get_, search_, screen_) with snake_case. This makes the tool set predictable and easy to navigate.

Tool Count1/5

With 91 tools, the server is far too large. The number of tools is excessive for a single MCP server, leading to cognitive overload and suggesting it should be split into multiple focused servers.

Completeness4/5

The tool surface covers an impressively wide domain including company data, insider trading, institutional holdings, political trading, and SEC filings. Minor gaps exist (e.g., no options or bonds), but the coverage is comprehensive for the stated purpose.

Resources