Signal8

Get SEC Filing Calendar

get_filing_calendar

Read-only

Get the forward-looking 10-K / 10-Q SEC filing-deadline calendar within a date window. Optionally restrict to a universe (sp500/ndx/dji/all) and/or a list of form types (default both 10-K and 10-Q).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_filing_calendar"
  }
}

Input Schema

Name	Required	Description
`to`	No	End date inclusive (YYYY-MM-DD, default today + 45d)
`from`	No	Start date inclusive (YYYY-MM-DD, default today)
`universe`	No	Optional index-universe filter (default "all")
`formTypes`	No	Optional SEC form types subset, e.g. ["10-Q"]

Output Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJul 4, 2026
- removedInput schema / properties / to / $ref
```
Removed value: -"#/properties/from"
```
- addedInput schema / properties / to / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
- addedInput schema / properties / to / type
```
Added value: +"string"
```
Changed9 schema fields changedJun 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / formTypes / description
```
Added value: +"Optional SEC form types subset, e.g. [\"10-Q\"]"
```
- addedInput schema / properties / from / description
```
Added value: +"Start date inclusive (YYYY-MM-DD, default today)"
```
- addedInput schema / properties / to / $ref
```
Added value: +"#/properties/from"
```
- addedInput schema / properties / to / description
```
Added value: +"End date inclusive (YYYY-MM-DD, default today + 45d)"
```
- removedInput schema / properties / to / pattern
```
Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
```
- removedInput schema / properties / to / type
```
Removed value: -"string"
```
- addedInput schema / properties / universe / description
```
Added value: +"Optional index-universe filter (default \"all\")"
```
- removedOutput schema / required
```
Removed value: -[
-  "data"
-]
```

Changed1 schema field changedJun 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {}
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedJun 27, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, and an output schema exists, so safety and return shape are covered elsewhere. The description adds real but modest behavioral detail: only 10-K and 10-Q forms are covered, and the form-type filter defaults to both. It says nothing about coverage breadth, pagination, or freshness of the deadline data.

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, both front-loaded with the core purpose first and the optional narrowing filters second. No filler, no restatement of the title.

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?

All four optional parameters are schema-documented, an output schema exists, and annotations cover the safety profile, so the description's job is mainly scope and defaults, which it does. Minor gap: it never states the coverage universe of companies whose deadlines are tracked, which matters for interpreting an empty result.

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 description coverage is 100%, so the baseline is 3, but the description adds a default not stated in the schema: formTypes defaults to both 10-K and 10-Q, and it clarifies that universe and form-type filters are independent and optional. It also frames from/to as a 'date window', reinforcing the inclusive-range semantics documented per-parameter.

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 gives a specific verb and resource: 'forward-looking 10-K / 10-Q SEC filing-deadline calendar'. That phrasing distinguishes it from nearby calendar tools (get_earnings_calendar, get_economic_calendar, get_legislative_calendar) and from retrospective filing tools (screen_sec_filings, search_sec_filings) without the agent needing to open another schema.

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?

'Forward-looking ... within a date window' establishes the use context clearly: upcoming deadlines, not past filings. It does not explicitly name an alternative or state when-not to use it (e.g. versus screen_sec_filings for historical filings), so it stops short of full routing guidance.

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

All Signal8 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.