Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official
by signal8ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Recent Material Filings

get_recent_material_filings
Read-only

Retrieve recent material 8-K filings (last 7 days) for S&P 500, Nasdaq-100, or Dow Jones constituents. Filter by specific 8-K item codes to focus on high-signal events like mergers, executive changes, or restructurings.

Instructions

Recent material 8-K filings (last 7 days) for the constituents of an index universe. By default returns the high-signal 8-K item codes (material agreements, M&A, executive changes, restructurings, etc.); pass items to filter to specific 8-K item codes. Choose the universe with universe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoOptional 8-K item codes (e.g. ["1.01","2.01"])
limitNoOptional max rows (1–100, default 50)
universeNoIndex universe to scan (sp500, ndx, or dji).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds behavioral details: time window (7 days), default high-signal item codes, and filtering options. It could mention default universe behavior but overall adds value.

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?

Two sentences, front-loaded with purpose, then parameter usage. Every sentence earns its place with zero waste.

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?

Covers time window, content type, default filtering, and parameter options. Output schema exists so return format is covered. Minor gap: default universe if not specified is not mentioned.

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. Description adds minimal context beyond schema: 'pass items to filter' and 'choose the universe'. It doesn't provide additional constraints or examples.

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 retrieves recent material 8-K filings (last 7 days) for index universe constituents, distinguishing it from sibling filing tools like get_filing_calendar which cover broader filing types.

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 explains when to use (to get high-signal 8-K filings for an index) and how to customize via items and universe. It lacks explicit when-not-to-use guidance, but the context is clear among siblings.

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

Deploy Server

Other Tools