AlphaCreek SEC Filings MCP

list_filings

Read-only

List available filings for a ticker (newest first) with artifact_document_id and dates. Use filing_registry=fca_nsm for UK FCA NSM reports. Use this first when you need a specific reporting period, including DEF 14A proxy statements (pass document_type=DEF 14A). Each row includes Filing metadata object. Includes document_type (Canonical document type. SEC: 10-K, 10-Q, 20-F, 6-K, 8-K, DEF 14A. FCA: annual, half-year, press.) and, for FCA press rows, announcement_type (FCA press subtype when document_type is press; null for annual and half-year. Values: 1st Quarter Results, 2nd Quarter Results, 3rd Quarter Results, 4th Quarter Results, Final Results, Preliminary Results, Share Buyback, Trading Update.).

Input Schema

Name	Required	Description	Default
`limit`	No
`ticker`	No
`company`	No
`document_type`	No	Optional document type filter (canonical values only). See Field reference for allowed values per registry.
`filing_registry`	No	Filing source registry. sec_edgar — US SEC EDGAR filings. fca_nsm — UK FCA National Storage Mechanism. Omit to search both registries.	sec_edgar

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

changedInput schema / properties / document_type / oneOf

Previous value: -[
-  {
-    "enum": [
-      "10-K",
-      "10-Q",
-      "20-F",
-      "6-K",
-      "8-K",
-      "annual",
-      "half-year",
-      "press"
-    ],
-    "type": "string"
-  },
-  {
-    "items": {
-      "enum": [
-        "10-K",
-        "10-Q",
-        "20-F",
-        "6-K",
-        "8-K",
-        "annual",
-        "half-year",
-        "press"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "enum": [
+      "10-K",
+      "10-Q",
+      "20-F",
+      "6-K",
+      "8-K",
+      "DEF 14A",
+      "annual",
+      "half-year",
+      "press"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "10-K",
+        "10-Q",
+        "20-F",
+        "6-K",
+        "8-K",
+        "DEF 14A",
+        "annual",
+        "half-year",
+        "press"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

Changed3 schema fields changedAug 6, 2026

changedInput schema / properties / document_type / description

Previous value: -"Optional filing type filter. SEC: 10-K, 10-Q, 20-F, 6-K, 8-K. FCA: Annual Report."New value: +"Optional document type filter (canonical values only). See Field reference for allowed values per registry."

changedInput schema / properties / document_type / oneOf

Previous value: -[
-  {
-    "enum": [
-      "10-K",
-      "10-Q",
-      "20-F",
-      "6-K",
-      "8-K",
-      "Annual Report"
-    ],
-    "type": "string"
-  },
-  {
-    "items": {
-      "enum": [
-        "10-K",
-        "10-Q",
-        "20-F",
-        "6-K",
-        "8-K",
-        "Annual Report"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "enum": [
+      "10-K",
+      "10-Q",
+      "20-F",
+      "6-K",
+      "8-K",
+      "annual",
+      "half-year",
+      "press"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "10-K",
+        "10-Q",
+        "20-F",
+        "6-K",
+        "8-K",
+        "annual",
+        "half-year",
+        "press"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

changedInput schema / properties / filing_registry / description

Previous value: -"Filing source registry. Use sec_edgar (default) for US SEC filings or fca_nsm for UK FCA NSM annual reports."New value: +"Filing source registry. sec_edgar — US SEC EDGAR filings. fca_nsm — UK FCA National Storage Mechanism. Omit to search both registries."

Changed3 schema fields changedJul 15, 2026

changedInput schema / properties / document_type / description

Previous value: -"Optional SEC filing type filter. One of 10-K, 10-Q, 20-F, 6-K, 8-K; comma-separated (e.g. 10-K,10-Q); or a JSON array string."New value: +"Optional filing type filter. SEC: 10-K, 10-Q, 20-F, 6-K, 8-K. FCA: Annual Report."

changedInput schema / properties / document_type / oneOf

Previous value: -[
-  {
-    "enum": [
-      "10-K",
-      "10-Q",
-      "20-F",
-      "6-K",
-      "8-K"
-    ],
-    "type": "string"
-  },
-  {
-    "items": {
-      "enum": [
-        "10-K",
-        "10-Q",
-        "20-F",
-        "6-K",
-        "8-K"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "enum": [
+      "10-K",
+      "10-Q",
+      "20-F",
+      "6-K",
+      "8-K",
+      "Annual Report"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "10-K",
+        "10-Q",
+        "20-F",
+        "6-K",
+        "8-K",
+        "Annual Report"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

addedInput schema / properties / filing_registry

Added value: +{
+  "default": "sec_edgar",
+  "description": "Filing source registry. Use sec_edgar (default) for US SEC filings or fca_nsm for UK FCA NSM annual reports.",
+  "enum": [
+    "sec_edgar",
+    "fca_nsm"
+  ],
+  "type": "string"
+}

Changed4 schema fields changedJun 13, 2026

addedInput schema / properties / document_type / description

Added value: +"Optional SEC filing type filter. One of 10-K, 10-Q, 20-F, 6-K, 8-K; comma-separated (e.g. 10-K,10-Q); or a JSON array string."

removedInput schema / properties / document_type / enum

Removed value: -[
-  "10-K",
-  "10-Q",
-  "20-F",
-  "6-K",
-  "8-K"
-]

addedInput schema / properties / document_type / oneOf

Added value: +[
+  {
+    "enum": [
+      "10-K",
+      "10-Q",
+      "20-F",
+      "6-K",
+      "8-K"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "10-K",
+        "10-Q",
+        "20-F",
+        "6-K",
+        "8-K"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / document_type / type
```
Removed value: -"string"
```

First observedJun 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds ordering (newest first) and the shape of each row (Filing metadata object with document_type/announcement_type), but says nothing about pagination behavior, auth, or the ticker-vs-company selection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and routing rule are front-loaded, which is good. But the trailing parentheticals enumerate document_type and announcement_type values that the input schema's enum already lists, adding length without new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully describes returned fields, and it covers registry and document_type filtering. It still omits the ticker/company relationship and limit behavior for a 5-parameter, zero-required tool, leaving the definition adequate but incomplete.

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 only 40%, so the description must compensate; it does explain document_type usage (DEF 14A example, canonical values) and the filing_registry= fca_nsm switch well. However, ticker, company, and limit are left unexplained in both schema and description, so the gap is only partially closed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (filings) with scope (for a ticker, newest first) plus returned identifiers (artifact_document_id and dates). It implicitly distinguishes itself from get_latest_filing by framing this as the full listing and by 'Use this first when you need a specific reporting period', though it does not name the siblings outright.

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?

Gives explicit when-to-use guidance ('Use this first when you need a specific reporting period') and a registry-selection rule ('Use filing_registry=fca_nsm for UK FCA NSM reports'). It stops short of naming alternatives like get_latest_filing or search_sec_event_filings and when to prefer them.

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

All AlphaCreek SEC Filings MCP 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.

Resources

Need Help?