AlphaCreek SEC Filings MCP

search_sec_event_filings

Read-only

Search US SEC 8-K and 6-K current-report nodes for company events and disclosures. Use this to discover issuers across a date range. Do not use this for 10-K or 10-Q filings. How to search:

Always pass concept_groups. Every group is required (AND). Within each group's any_of list, one alternative must match (OR). All groups match inside one filing node. Use separate groups for the main context, action or direction, business object or metric, and a causal or limiting relation when that relation is essential.
Optionally pass query with likely verbatim disclosure phrases. Each item is an exact adjacent-token phrase. Put alternate full phrasings in the same list. Query plus concept_groups is hybrid search: exact phrase matches receive a score boost, and concept groups recover different wording. Do not put broad topic words such as "China", "AI", "customer", or "restructuring" alone in query.
Add real synonyms and alternate filing language to any_of. The concept path uses English stemming, so one base form usually covers inflections (decline/declined/declining and volume/volumes). Stemming does not add synonyms (sales does not mean revenue; reduce does not mean weaken).
Do not search with query only. Omit query for concept-only search. If query is omitted, the search is concept-only.
Use date filters for time and tickers to search only selected issuers. Pass ne_tickers (or prefix a symbol with !) to omit issuers.
Results are candidates, not final conclusions. Call read_node_content with each promising document_id and node_id(s). Verify negation, causal claims, comparisons across periods, and numeric thresholds such as a percentage or dollar amount in the source text. Cite CITATION_MARKDOWN. When you finish an issuer, search again with the same inputs and add its ticker to ne_tickers so later hits come from other issuers. Examples of useful group dimensions include geography + weakening signal + demand metric; CapEx + reduction + guidance; AI/automation + enablement + workforce + reduction; customer + loss/concentration; data centers + exposure + monetization; or restructuring + program/charge. Do not add a group for a detail that the filing may leave implicit, because every group is mandatory. Each result is one filing node: document_id, node_id, parent_node_id, ticker, type, filing_date, match_mode, query, score, and a short snippet.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum unique matches to return across all query phrases. At most 3 matches come from one filing.
`query`	No	Optional exact disclosure phrases for hybrid search (max 8). Each phrase requires adjacent tokens in order and does not use stemming. Send complete event phrasings, not standalone topics. Omit this field for concept-only search. Examples: ["reduced capital expenditures", "lower capital spending"]; ["lost a major customer", "termination by our largest customer"]; ["workforce reduction", "reduce headcount"].
`tickers`	No	Optional. Search only these issuers (example: ["NVDA", "MSFT"]). Prefix a symbol with ! to omit it (same as ne_tickers). Max 50. Omit to search all issuers.
`end_date`	Yes	Inclusive end date on filing_date (YYYY-MM-DD)
`ne_tickers`	No	Optional. Omit these issuers (example: ["HOOD"] or ["!HOOD"]). After you finish read_node_content for a ticker, search again with that ticker here. Exclude wins if a ticker is in both lists. Max 50.
`start_date`	Yes	Inclusive start date on filing_date (YYYY-MM-DD)
`concept_groups`	Yes	Required stemmed concept groups. Every group must match in the same node (AND). Any one alternative inside any_of can satisfy its group (OR). Use 2-5 focused groups in most searches. Supply synonyms and alternate filing terms, but omit simple inflections because English stemming handles them. Do not use this field to prove numeric thresholds, negation, causality, or changes across several filings; retrieve candidates and verify those claims with read_node_content.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 2, 2026

changedInput schema / properties / concept_groups / description

Previous value: -"Optional stemmed concept fallback for broad discovery. Every group must match in the same node (AND). Any one alternative inside any_of can satisfy its group (OR). Use 2-5 focused groups in most searches. Supply synonyms and alternate filing terms, but omit simple inflections because English stemming handles them. Do not use this field to prove numeric thresholds, negation, causality, or changes across several filings; retrieve candidates and verify those claims with read_node_content."New value: +"Required stemmed concept groups. Every group must match in the same node (AND). Any one alternative inside any_of can satisfy its group (OR). Use 2-5 focused groups in most searches. Supply synonyms and alternate filing terms, but omit simple inflections because English stemming handles them. Do not use this field to prove numeric thresholds, negation, causality, or changes across several filings; retrieve candidates and verify those claims with read_node_content."

changedInput schema / properties / query / description

Previous value: -"Required exact disclosure phrases (max 8). Each phrase requires adjacent tokens in order and does not use stemming. Send complete event phrasings, not standalone topics. Examples: [\"reduced capital expenditures\", \"lower capital spending\"]; [\"lost a major customer\", \"termination by our largest customer\"]; [\"workforce reduction\", \"reduce headcount\"]."New value: +"Optional exact disclosure phrases for hybrid search (max 8). Each phrase requires adjacent tokens in order and does not use stemming. Send complete event phrasings, not standalone topics. Omit this field for concept-only search. Examples: [\"reduced capital expenditures\", \"lower capital spending\"]; [\"lost a major customer\", \"termination by our largest customer\"]; [\"workforce reduction\", \"reduce headcount\"]."

changedInput schema / required

Previous value: -[
-  "query",
-  "start_date",
-  "end_date"
-]New value: +[
+  "concept_groups",
+  "start_date",
+  "end_date"
+]

Changed8 schema fields changedAug 29, 2026

addedInput schema / properties / concept_groups

Added value: +{
+  "description": "Optional stemmed concept fallback for broad discovery. Every group must match in the same node (AND). Any one alternative inside any_of can satisfy its group (OR). Use 2-5 focused groups in most searches. Supply synonyms and alternate filing terms, but omit simple inflections because English stemming handles them. Do not use this field to prove numeric thresholds, negation, causality, or changes across several filings; retrieve candidates and verify those claims with read_node_content.",
+  "examples": [
+    [
+      {
+        "any_of": [
+          "capital expenditure",
+          "CapEx",
+          "capital spending"
+        ],
+        "name": "capital_spending"
+      },
+      {
+        "any_of": [
+          "reduce",
+          "lower",
+          "cut"
+        ],
+        "name": "direction"
+      },
+      {
+        "any_of": [
+          "guidance",
+          "outlook",
+          "expect"
+        ],
+        "name": "forward_looking"
+      }
+    ]
+  ],
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "any_of": {
+        "description": "Synonyms or short phrases for one required concept. Any one can match. Multiword values are adjacent-token phrases. English stemming applies.",
+        "items": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 16,
+        "minItems": 1,
+        "type": "array"
+      },
+      "name": {
+        "description": "Short role label, such as geography, direction, business_metric, technology, or customer_event.",
+        "maxLength": 64,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "any_of"
+    ],
+    "type": "object"
+  },
+  "maxItems": 6,
+  "minItems": 2,
+  "type": "array"
+}

changedInput schema / properties / limit / default
```
Previous value: -20New value: +30
```

changedInput schema / properties / limit / description

Previous value: -"Maximum exact-match results to return"New value: +"Maximum unique matches to return across all query phrases. At most 3 matches come from one filing."

addedInput schema / properties / ne_tickers

Added value: +{
+  "description": "Optional. Omit these issuers (example: [\"HOOD\"] or [\"!HOOD\"]). After you finish read_node_content for a ticker, search again with that ticker here. Exclude wins if a ticker is in both lists. Max 50.",
+  "oneOf": [
+    {
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "items": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 50,
+      "minItems": 1,
+      "type": "array"
+    }
+  ]
+}

changedInput schema / properties / query / description

Previous value: -"Exact phrase to search for, e.g. private credit"New value: +"Required exact disclosure phrases (max 8). Each phrase requires adjacent tokens in order and does not use stemming. Send complete event phrasings, not standalone topics. Examples: [\"reduced capital expenditures\", \"lower capital spending\"]; [\"lost a major customer\", \"termination by our largest customer\"]; [\"workforce reduction\", \"reduce headcount\"]."

addedInput schema / properties / query / oneOf

Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "items": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 8,
+    "minItems": 1,
+    "type": "array"
+  }
+]

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

addedInput schema / properties / tickers

Added value: +{
+  "description": "Optional. Search only these issuers (example: [\"NVDA\", \"MSFT\"]). Prefix a symbol with ! to omit it (same as ne_tickers). Max 50. Omit to search all issuers.",
+  "oneOf": [
+    {
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "items": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 50,
+      "minItems": 1,
+      "type": "array"
+    }
+  ]
+}

AddedAug 12, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, and the description adds valuable behavioral detail: concept groups are AND-ed across groups and OR-ed within any_of, query uses exact adjacent-token phrases with score boosting, stemming does not add synonyms, and results are candidates that must be verified in source text. No contradiction 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.

Conciseness5/5

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

The description is long but logically structured with numbered search rules, examples, and a result-field list. Every section earns its place for a complex search tool, and the main purpose and scope are front-loaded in the first sentences.

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 no output schema, the description explicitly lists every result field and explains how to consume results via read_node_content. It also covers hybrid search behavior, required parameters, and workflow limitations, leaving no critical gap for an agent to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds substantial strategy beyond the schema: it explains how to build concept_groups, what not to put in query, how stemming behaves, and how tickers/ne_tickers should be used across repeated searches. The description compensates and enriches every parameter's meaning.

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: 'Search US SEC 8-K and 6-K current-report nodes for company events and disclosures.' It also names the intended use ('discover issuers across a date range') and an explicit scope exclusion ('Do not use this for 10-K or 10-Q filings'), which clearly separates it from sibling filing-lookup tools.

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?

Provides explicit when-to-use context and a when-not ('Do not use for 10-K or 10-Q filings'). It gives a full search workflow, including forming concept groups, using query phrases, excluding tickers via ne_tickers, and following up with read_node_content. This is strong, actionable guidance beyond the schema.

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?