Skip to main content
Glama

Stratalize Intelligence

Get Sec Insider Trading

get_sec_insider_trading
Read-only

SEC Form 4 insider transaction history — executive buy/sell filings in the last 90 days with filing dates and links. Returns insider activity signal. Source: SEC EDGAR. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_sec_insider_trading"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so safety is covered. The description usefully adds the 90-day window, the SEC EDGAR source, a per-call price of $0.02 USDC, and attestation/verification details — but is vague about the shape of the 'insider activity signal' it returns. That is real added context, above a baseline 3 but short of rich behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core sentence is well front-loaded and efficient. However, roughly half the text is promotional boilerplate about post-quantum signed settlement receipts and a verification URL, which is less actionable than the pricing and date-window facts that surround it.

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?

For a simple single-parameter, read-only lookup with annotations present and no output schema, the basics are covered. Still missing are the ticker format expectation and any indication of the return structure ('insider activity signal' is undefined), which an agent needs to call it confidently.

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

Parameters2/5

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

There is one required parameter, 'ticker', with 0% schema description coverage and no enum or format constraints beyond min/max length. The description never mentions the ticker argument, its format (e.g. 'AAPL' vs 'AAPL.US'), or whether non-US listings are accepted, so it does not compensate for the schema gap.

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?

States a specific verb+resource: SEC Form 4 insider transaction history, scoped to executive buy/sell filings in the last 90 days. Clear to an agent, though it never distinguishes itself from the sibling get_form4_insider_cluster, so the caller must infer which one gives per-filing history versus cluster aggregates.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative. 'Returns insider activity signal' only implies the use case; with a closely related sibling present, the description leaves the routing decision to the agent.

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