Skip to main content
Glama

Antigravity x402 & MCP Gateway

fetch_sec_insider_and_8k

[0.010000 USDC via x402] Resolves any US public equity ticker, 10-digit CIK, company name, or theme against SEC EDGAR submissions and EFTS full-text index to extract recent Form 4 insider filings, decoded Form 8-K item catalysts (1.01 Material Agreement, 2.02 Earnings, 5.02 Officer Change, 7.01 Reg FD, 8.01 Other), and 90-day activity band.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fetch_sec_insider_and_8k"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum recent Form 4 and Form 8-K filings to return (1 to 25, default 8).
queryNoStock ticker (e.g., 'NVDA', 'AAPL', 'MSFT', 'TSLA', 'COIN'), 10-digit CIK, company name, or event keyword.
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.010000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the critical behavioral fact: the call is paid, costing 0.010000 USDC via x402, with the schema completing the payment handshake (omit signature to receive a quote). It also discloses what is returned (recent Form 4 filings, decoded 8-K catalysts, a 90-day activity band). Gaps remain on failure modes when payment is rejected, rate limits, and result ordering, which keeps it below 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?

It is a single front-loaded sentence with the price signal first and the output enumeration last; every clause carries information and nothing is padded. The one weakness is density: the trailing '90-day activity band' is an undefined term crammed into an already long sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must explain return values, and it does so only at a high level (Form 4, 8-K items, activity band) without field names, ordering, or structure. For a tool that merges two SEC sources and involves a payment step, missing detail on what happens on payment failure or empty results leaves a real gap.

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 all three parameters are already documented in the schema, and the description mostly restates them (identifier types, recent filings). It adds no format detail beyond the schema, such as how 'theme' keywords map to EFTS queries. Baseline 3 is appropriate when structured data does the heavy lifting.

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 gives a specific verb ('Resolves ... to extract') and a precisely scoped resource: SEC EDGAR submissions plus the EFTS full-text index, yielding Form 4 insider filings and decoded Form 8-K items. The enumerated 8-K item codes (1.01, 2.02, 5.02, 7.01, 8.01) make the scope unambiguous. It never names a sibling, so an agent must infer that this is not the Form D tool or the FDIC/bank-health tools from content alone.

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

Usage Guidelines2/5

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

It states what identifiers are accepted ('any US public equity ticker, 10-digit CIK, company name, or theme') but gives no when-to-use, when-not-to-use, or alternative-tool guidance. Nothing tells an agent whether this is the right call versus fetch_sec_form_d_startup_leads or the other SEC-adjacent siblings. The x402 price tag is operational context, not usage routing.

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.