Skip to main content
Glama

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

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-schema context: the upstream source (SEC EDGAR), the fixed 90-day lookback window, and the per-call price of $0.02 USDC, which matters for an agent making cost tradeoffs. The attestation/verify sentences are promotional boilerplate that do not contradict annotations but add little operational meaning.

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 purpose and scope are front-loaded and the source and price sentences earn their place. But roughly a third of the text is marketing material about a post-quantum signed settlement receipt and a verification URL, which is not actionable for tool selection. Tightening to two or three sentences would improve 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?

The tool is simple (one parameter, no output schema) and annotations cover its read-only, open-world nature. Still, the description leaves the required ticker format undocumented and describes the return only as an 'insider activity signal' plus filing dates and links, without stating structure, whether an empty result is possible, or error behavior for unknown tickers.

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?

Schema description coverage is 0%, so the single required `ticker` parameter is documented nowhere. The description only implies that the query is company-scoped and never mentions the parameter, its format, or examples such as 'AAPL'. With low coverage the description was expected to compensate and does not.

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 names a specific resource and verb: SEC Form 4 insider transaction history, executive buy/sell filings, with a stated 90-day window and included fields (filing dates and links). It is far more specific than the tool name alone. However, it never distinguishes itself from the sibling get_form4_insider_cluster, which an agent could easily confuse with this one.

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 statement of when to use this tool versus alternatives such as get_form4_insider_cluster or get_sec_beneficial_ownership. The 90-day window is a scope constraint, not usage guidance, and no exclusions or prerequisites are given. The agent must infer selection criteria from the tool names alone.

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