Skip to main content
Glama

AlphaCreek SEC Filings MCP

search_sec_event_filings

Read-only

Search US SEC filing nodes for a disclosure claim. The search covers 8-K, 6-K, 10-K, 10-Q, and 20-F. Omit document_type to search all of those forms. Pass document_type to search only the forms you name. Do not use this for DEF 14A. How to search:

  1. Always pass concept_groups. Every group is required (AND). Within each group's any_of list, one alternative must match (OR). Use 2-5 groups for separate parts of the claim: topic, action, metric, and a causal link when that link is essential. Example: geography + weaker demand + decline, or AI + productivity + margin. Add synonyms. English stemming covers inflections (decline/declined), not synonyms (sales is not revenue). Do not add a group for a detail the filing may leave implicit.

  2. query is optional. Each item is an exact adjacent-token phrase. Put alternate full phrasings in the same list. Query plus concept_groups is hybrid search: an exact phrase ranks first, so a generic phrase such as "margin expansion" can outrank the causal sentence you want. Prefer phrases that state the relationship. Do not pass a broad topic word alone. Do not search with query only. Omit query for concept-only search.

  3. start_date and end_date are required. tickers limits issuers. Optional document_type limits the search to one or more of 8-K, 6-K, 10-K, 10-Q, and 20-F. Omit it to search all of those forms. How to continue:

  4. Each call returns one page. There is no total count. If HAS_MORE is true, call again with cursor set to NEXT_CURSOR and the same concept_groups, dates, query, tickers, ne_tickers, document_type, and match_scope. A cursor from different inputs is rejected. An empty page with HAS_MORE true is not the end: call again with that cursor. Stop when HAS_MORE is false or when later pages are not relevant.

  5. If a page is mostly co-occurrence (the terms appear, but not the claim), start a new search with no cursor. Add a concept group or exact causal phrases. If a page is too sparse, start a new search with no cursor and drop the least essential group. Do not change filters while passing a cursor.

  6. ne_tickers excludes issuers you have already reviewed. It does not load the next page. Results are candidates. Call read_node_content with document_id and node_id. node_id may start with sp-. Verify negation, causality, comparisons across periods, and numeric thresholds in the source text. Cite CITATION_MARKDOWN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum matches on this page. Not a total count. At most 3 matches come from one filing. When HAS_MORE is true, pass cursor to read the next page.
queryNoOptional 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"].
cursorNoPage id from the previous NEXT_CURSOR line. Copy it unchanged. Pass it only with the same concept_groups, dates, query, tickers, ne_tickers, document_type, and match_scope. A mismatch is rejected. Omit it to start a new search.
tickersNoOptional. 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_dateYesInclusive end date on filing_date (YYYY-MM-DD)
ne_tickersNoOptional. Omit these issuers (example: ["HOOD"] or ["!HOOD"]). This does not load the next page. Use cursor for that. Exclude wins if a ticker is in both lists. Max 50.
start_dateYesInclusive start date on filing_date (YYYY-MM-DD)
match_scopeNonode (default): Atlas ranks every matching filing node. window is accepted for compatibility and behaves like node.node
document_typeNoOptional. Limit the search to one or more of "8-K", "6-K", "10-K", "10-Q", and "20-F". Omit to search all of those forms.
concept_groupsYesRequired stemmed concept groups. Every group must match (AND). Any one alternative inside any_of can satisfy its group (OR). Atlas ranks the matching filing nodes. 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.

  1. Changed5 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque NEXT_CURSOR from the previous response. Pass it with the same concept_groups, dates, query, tickers, ne_tickers, document_type, and match_scope to read the next page. Omit it to start from the first page."New value: +"Page id from the previous NEXT_CURSOR line. Copy it unchanged. Pass it only with the same concept_groups, dates, query, tickers, ne_tickers, document_type, and match_scope. A mismatch is rejected. Omit it to start a new search."
    • changedInput schema / properties / document_type / description
      Previous value: -"Optional. Search only these current-report forms: \"8-K\", \"6-K\", or both. Omit to search 8-K and 6-K."New value: +"Optional. Limit the search to one or more of \"8-K\", \"6-K\", \"10-K\", \"10-Q\", and \"20-F\". Omit to search all of those forms."
    • changedInput schema / properties / document_type / oneOf
      Previous value: -[
      -  {
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "items": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "maxItems": 2,
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "maxItems": 5,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum matches to return on this page. At most 3 matches come from one filing. When has_more is true, pass cursor to read the next page."New value: +"Maximum matches on this page. Not a total count. At most 3 matches come from one filing. When HAS_MORE is true, pass cursor to read the next page."
    • changedInput schema / properties / ne_tickers / description
      Previous value: -"Optional. Omit these issuers (example: [\"HOOD\"] or [\"!HOOD\"]). This filter does not load the next page. Use cursor for that. Exclude wins if a ticker is in both lists. Max 50."New value: +"Optional. Omit these issuers (example: [\"HOOD\"] or [\"!HOOD\"]). This does not load the next page. Use cursor for that. Exclude wins if a ticker is in both lists. Max 50."
  2. Changed6 schema fields changed
    • changedInput schema / properties / concept_groups / description
      Previous 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."New value: +"Required stemmed concept groups. Every group must match (AND). Any one alternative inside any_of can satisfy its group (OR). Atlas ranks the matching filing nodes. 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."
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Opaque NEXT_CURSOR from the previous response. Pass it with the same concept_groups, dates, query, tickers, ne_tickers, document_type, and match_scope to read the next page. Omit it to start from the first page.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / document_type
      Added value: +{
      +  "description": "Optional. Search only these current-report forms: \"8-K\", \"6-K\", or both. Omit to search 8-K and 6-K.",
      +  "oneOf": [
      +    {
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "items": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "maxItems": 2,
      +      "minItems": 1,
      +      "type": "array"
      +    }
      +  ]
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum unique matches to return across all query phrases. At most 3 matches come from one filing."New value: +"Maximum matches to return on this page. At most 3 matches come from one filing. When has_more is true, pass cursor to read the next page."
    • addedInput schema / properties / match_scope
      Added value: +{
      +  "default": "node",
      +  "description": "node (default): Atlas ranks every matching filing node. window is accepted for compatibility and behaves like node.",
      +  "enum": [
      +    "window",
      +    "node"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / ne_tickers / description
      Previous value: -"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."New value: +"Optional. Omit these issuers (example: [\"HOOD\"] or [\"!HOOD\"]). This filter does not load the next page. Use cursor for that. Exclude wins if a ticker is in both lists. Max 50."
  3. Changed3 schema fields changed
    • 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"
      +]
  4. Changed8 schema fields changed
    • 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"
      +    }
      +  ]
      +}
  5. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/destructiveHint; the description goes well beyond by disclosing pagination semantics (one page per call, no total count, HAS_MORE/NEXT_CURSOR, cursor rejected on mismatched inputs, empty page with HAS_MORE still requiring another call), a max-3-matches-per-filing cap, and the hybrid-ranking behavior where a generic exact phrase can outrank the intended sentence.

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?

Long but deliberately structured with numbered sections, front-loaded purpose, and no filler sentences; each rule carries operational weight. Slightly verbose repetition of the document_type/all-forms rule (stated twice) is the only waste.

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 and 10 parameters, the description still covers return shape (paged candidates, HAS_MORE/NEXT_CURSOR, CITATION_MARKDOWN), the verification requirement for negation/causality/numeric claims, and the follow-up call signature. Nothing an agent needs to invoke or continue correctly is missing.

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 meaningfully extends it: it explains why query plus concept_groups is hybrid search, warns that generic phrases can dominate, states that query must state a relationship and never be used alone, and clarifies ne_tickers does not page. These are semantics an agent cannot infer from the schema alone.

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?

Specific verb+resource (search US SEC filing nodes for a disclosure claim) with explicit coverage of the five form types and an explicit exclusion (DEF 14A). It also names the downstream sibling read_node_content, so an agent can place it in a workflow without opening 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 Guidelines5/5

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

Gives explicit when-to-use, when-not (DEF 14A), how to build concept_groups vs query, and full continuation rules including cursor reuse constraints and the no-cursor restart strategy for poor pages. Alternative tool (read_node_content) is named along with the verification it performs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources