AlphaCreek SEC Filings MCP

get_latest_filing

Read-only

Return latest filing metadata for a company or ticker. If ticker and company are omitted, return newly ingested filings newest-first. Omit filing_registry in that mode to include both SEC and FCA. Company results include one metadata object; newly ingested results include a filings list. Each row includes Filing metadata object. Includes document_type (Canonical document type. SEC: 10-K, 10-Q, 20-F, 6-K, 8-K. 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

TableJSON Schema

Name	Required	Description
`limit`	No	Max newly ingested filings when ticker and company are omitted
`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. fca_nsm — UK FCA NSM. Omit with no ticker/company to list newly ingested filings from both registries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 18, 2026

removedInput schema / properties / filing_registry / default
```
Removed value: -"sec_edgar"
```

changedInput schema / properties / filing_registry / description

Previous value: -"Filing source registry. sec_edgar — US SEC EDGAR filings. fca_nsm — UK FCA National Storage Mechanism. Omit to search both registries."New value: +"Filing source registry. sec_edgar — US SEC EDGAR. fca_nsm — UK FCA NSM. Omit with no ticker/company to list newly ingested filings from both registries."

addedInput schema / properties / limit

Added value: +{
+  "default": 25,
+  "description": "Max newly ingested filings when ticker and company are omitted",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

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

A4.1/5.0

Behavior4/5

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

The description adds significant behavioral context beyond the annotations (readOnlyHint, destructiveHint). It explains the two distinct result structures (one metadata object vs. a filings list), details the document_type and announcement_type fields, and describes how parameter combinations affect behavior. No contradictions with annotations.

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

Conciseness4/5

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

The description is front-loaded with the main purpose and then systematically explains modes and field details. It is slightly verbose but every sentence adds value. The structure is logical and easy to parse.

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?

Given the complexity (two modes, multiple parameters, no output schema), the description is remarkably complete. It covers all parameter combinations, result structures, field meanings, and enum values. The agent has sufficient information to decide when and how to use the 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?

With 60% schema description coverage, the description compensates by explaining the effect of omitting ticker/company, the role of filing_registry, and the meaning of document_type values including FCA press subtypes. This adds value beyond the schema, though ticker and company parameters lack explicit descriptions.

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?

The description clearly states the tool returns the latest filing metadata for a company or ticker and explains both modes (with company/ticker and without). It is specific about the verb and resource, but does not explicitly differentiate from sibling tools like get_filing_toc or list_filings, so a 4 is appropriate.

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 provides explicit guidance on when to use each mode: with ticker/company for a specific company, or omit them for newly ingested filings. It also advises omitting filing_registry in the latter mode to include both SEC and FCA. This is clear contextual guidance, though it does not list alternative tools or when to avoid.

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?