Signal8 MCP Server

Official

by signal8ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get Exhibit Content

get_exhibit_content

Read-only

Retrieve full text/HTML content of an SEC filing exhibit, including exhibit type, description, company name, and form type. Truncate large exhibits with maxLength parameter.

Instructions

Get the full text/HTML content of a single exhibit from an SEC filing. Returns the exhibit text along with exhibit_type, description, company_name, accession_number, and form_type. Use the maxLength parameter to truncate large exhibits. Find exhibit IDs using get_filing_exhibits first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Exhibit ID (numeric). Find via get_filing_exhibits.
`maxLength`	No	Truncate content to this many characters. Response includes a "truncated" boolean.

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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds value by explaining truncation behavior and the truncated boolean in the response. No contradictions.

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 concise sentences: purpose, return fields, usage hint. No filler, every sentence adds value.

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 an output schema present, the description covers input, usage, and behavior fully. No missing information for an AI agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions. The description adds context about maxLength truncation and the truncated response field, going beyond schema.

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 it gets the full text/HTML content of a single exhibit from an SEC filing, with a specific verb and resource. It distinguishes from siblings by referencing get_filing_exhibits for finding IDs.

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?

It explicitly instructs to use get_filing_exhibits first to find exhibit IDs and mentions the maxLength parameter for truncation. While it doesn't list when not to use, the guidance is clear and actionable.

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

Deploy Server