AlphaCreek SEC Filings MCP

get_filing_toc

Read-only

Return the full filing table of contents for one filing. If artifact_document_id is omitted, resolves the single latest filing for ticker/company (and optional document_type) only. Use list_filings first to discover a specific reporting period. Pass document_type=DEF 14A for US proxy statements. For DEF 14A, TOC rows are native proxy section labels when the filing has a linked HTML TOC; otherwise they use sec-parser headings. For FCA filings, pass filing_registry=fca_nsm; TOC node ids are HTML page element ids (e.g. pf2a, page12, pageView1) for annual ESEF reports or sec-parser ids (e.g. sp-0000001) for half-year RNS HTML reports.

Input Schema

Name	Required	Description	Default
`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
`artifact_document_id`	No

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

A4.5/5.0

Behavior4/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 genuine behavioral context beyond that: the implicit latest-filing resolution when artifact_document_id is omitted, and the differing TOC row/id formats by document type and registry. Auth, rate limits, and pagination are not addressed.

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?

Front-loaded with the core purpose before the conditional details. The registry-specific id examples (pf2a, page12, sp-0000001) are dense but useful; the description is long for a single paragraph, though nearly every clause carries actionable information.

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?

With no output schema, the description carries return-value burden and partially does so by describing what TOC rows contain (native proxy section labels vs. sec-parser headings, HTML element ids vs. sec-parser ids). It stops short of describing the overall response shape, such as node id/title structure or whether content is included.

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 only 40%, so the description must compensate and largely does: it explains omission behavior for artifact_document_id, the special DEF 14A value for document_type, and the fca_nsm value for filing_registry. ticker vs. company precedence is implied ('ticker/company') but never spelled out.

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?

States a specific verb and resource: 'Return the full filing table of contents for one filing.' The scoping sentence about omitted artifact_document_id ('resolves the single latest filing for ticker/company') makes the tool's behavior distinguishable from siblings like list_filings and get_latest_filing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'Use list_filings first to discover a specific reporting period,' and gives conditional guidance for proxies ('Pass document_type=DEF 14A') and UK filings ('pass filing_registry=fca_nsm'). An agent knows both the prerequisite and the branch conditions without inference.

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?