Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Recent Material Filings

get_recent_material_filings
Read-only

Retrieve recent material 8-K filings from the last 7 days for S&P 500, Nasdaq-100, or Dow Jones constituents. Filter by specific 8-K item codes and limit results.

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
Behavior3/5

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

Annotations already provide readOnlyHint=true. The description adds the time range (last 7 days) and default item filtering. No mention of rate limits or auth, but adequate given annotations.

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, efficient. No redundant information.

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, no need to describe returns. The description covers time range, default filtering, universe choice, and optional parameters. Complete for a filtered-list tool.

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%. The description adds meaning by explaining default behavior for items (high-signal codes) and the role of universe. It goes beyond the basic schema descriptions.

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 returns recent material 8-K filings for index constituents, with default high-signal items and optional filtering. It distinguishes from siblings by specifying 'recent material 8-K filings' and 'index universe'.

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 explicitly tells when to use the tool (for recent material filings) and how to filter by items and universe. It does not explicitly state when not to use it or list alternatives, but the context is clear.

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