topai-mcp-suite

Overview Schema Source Related Servers Discussions Admin

edgarpulse_parse_filing

Read-onlyIdempotent

Parses raw SEC Form 4 and 8-K XML to extract C-suite insider transactions, cluster purchases, vesting events, and conviction scores for tracking executive sentiment in financial workflows.

Instructions

Parses raw SEC Form 4 and Form 8-K XML filings to extract C-suite insider transactions, open-market cluster purchases, vesting events, and calculate quantitative managerial conviction scores. Use when: Tracking corporate executive open-market purchases, insider sentiment, and institutional governance changes in financial workflows. Do not use when: Anonymizing SQL databases or evaluating container layer bloat. Alternative: Use sqltwin_stream_anonymize for database sanitization, or dockerlean_wasm_audit for container optimization. Execution: Runs locally in-memory (<5ms), read-only, idempotent, zero network calls, zero telemetry, air-gapped deterministic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filingXml": "<filingXml>"
    },
    "name": "edgarpulse_parse_filing"
  }
}

Input Schema

Name	Required	Description	Default
`filingXml`	Yes	Raw XML content of SEC EDGAR Form 4 or Form 8-K filing.
`licenseKey`	No	Optional TopAI Sovereign Pro offline license key (or set TOPAI_LICENSE_KEY env variable).

Output Schema

Name	Required	Description
`issuer`	Yes	Stock symbol / ticker of the reporting corporate issuer.
`transactions`	Yes	List of parsed transaction records including shares, price, and acquisition codes.
`transactionsCount`	Yes	Number of parsed insider transaction events.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.6Oct 22, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / filingXml / description

Previous value: -"Raw SEC XML filing content"New value: +"Raw XML content of SEC EDGAR Form 4 or Form 8-K filing."

addedInput schema / properties / licenseKey

Added value: +{
+  "description": "Optional TopAI Sovereign Pro offline license key (or set TOPAI_LICENSE_KEY env variable).",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "issuer": {
+      "description": "Stock symbol / ticker of the reporting corporate issuer.",
+      "type": "string"
+    },
+    "transactions": {
+      "description": "List of parsed transaction records including shares, price, and acquisition codes.",
+      "type": "array"
+    },
+    "transactionsCount": {
+      "description": "Number of parsed insider transaction events.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "issuer",
+    "transactionsCount",
+    "transactions"
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful execution context: local in-memory operation, sub-5ms latency, zero network calls and telemetry, deterministic. That is largely reinforcing the openWorld/readOnly annotations rather than revealing new failure modes (e.g., what happens with malformed XML), so it stops short of a 5.

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?

Purpose is front-loaded in the first sentence, and the Use/Do-not-use/Alternative/Execution structure is scannable. The negative examples about anonymizing SQL databases and container bloat are somewhat contrived filler for a domain that has no plausible overlap, costing a small amount of efficiency.

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?

An output schema exists, so return values need no explanation, and the description covers purpose, routing, and runtime characteristics. The one gap is the licensing dimension: `licenseKey` implies a gated Pro tier, but the description never says whether parsing is degraded or blocked without a key, which is behaviorally relevant.

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 description coverage is 100%, so both `filingXml` and `licenseKey` are already documented in the schema, and 3 is the baseline. The description adds no format, size, or encoding guidance for the XML payload, nor any note on when the Pro license key is required, so it does not exceed the schema.

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 (parses) and resource (SEC Form 4 and Form 8-K XML filings) and enumerates the exact outputs: insider transactions, cluster purchases, vesting events, conviction scores. The sibling list is entirely unrelated domains, and the description preemptively names two of them as non-overlapping, so an agent can select this tool unambiguously.

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?

Explicit 'Use when' (executive open-market purchases, insider sentiment, governance changes) and 'Do not use when' (SQL anonymization, container layer bloat) with named alternatives `sqltwin_stream_anonymize` and `dockerlean_wasm_audit`. This is the full when/when-not/alternative triad with no inference required.

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

Deploy Server