Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Edgar Insider Transactions

edgar_insider_transactions
Read-onlyIdempotent

AUTHORITATIVE insider trading activity (SEC Form 3/4/5) for a US public company — who bought or sold, how many shares, at what price, and what they hold now. Send the company as ticker_or_cik — a ticker ("TSLA") or a CIK — and cik / ticker are accepted as aliases for it. Returns each recent Form 4 filing parsed into structured transactions: reporting owner + role (director/officer/10% holder), transaction code (P=open-market purchase, S=sale, A=grant/award, M=option exercise, G=gift, F=tax-withholding), shares, price per share, acquired/disposed, and shares owned after. Use for "insider buying at $TICKER", "did executives sell recently", "latest Form 4 activity". Open-market purchases (code P) are the strongest conviction signal; awards (code A) are routine comp. For the raw filing list use edgar_company_filings with form_type:"4".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoAlias for `ticker_or_cik` — the spelling edgar_company_concept and edgar_company_facts use for the same thing. Takes a ticker or a CIK.
limitNoMax Form 4/3/5 filings to parse (1-25, default 10)
tickerNoAlias for `ticker_or_cik` — the spelling edgar_fund_holdings and edgar_ticker_to_cik use for the same thing. Takes a ticker or a CIK.
ticker_or_cikNoREQUIRED (or one of its aliases `cik` / `ticker`). Ticker symbol (e.g., "TSLA") or CIK number (e.g., "1318605")
include_derivativesNoAlso include derivative (options/RSU) transactions. Default false (non-derivative common-stock only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cik
      Added value: +{
+  "description": "Alias for `ticker_or_cik` — the spelling edgar_company_concept and edgar_company_facts use for the same thing. Takes a ticker or a CIK.",
+  "type": "string"
+}
    • addedInput schema / properties / ticker
      Added value: +{
+  "description": "Alias for `ticker_or_cik` — the spelling edgar_fund_holdings and edgar_ticker_to_cik use for the same thing. Takes a ticker or a CIK.",
+  "type": "string"
+}
    • changedInput schema / properties / ticker_or_cik / description
      Previous value: -"Ticker symbol (e.g., \"TSLA\") or CIK number (e.g., \"1318605\")"New value: +"REQUIRED (or one of its aliases `cik` / `ticker`). Ticker symbol (e.g., \"TSLA\") or CIK number (e.g., \"1318605\")"
    • changedInput schema / required
      Previous value: -[
-  "ticker_or_cik"
-]New value: +[]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "ticker_or_cik": "TSLA"
+  },
+  {
+    "include_derivatives": true,
+    "ticker_or_cik": "1318605"
+  }
+]
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context by decoding transaction codes (P, S, A, M, G, F), explaining that P is the strongest conviction signal and A is routine compensation, and describing the parsed output structure. This goes well beyond the annotations.

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

Conciseness5/5

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

Every sentence contributes: purpose, input identification, output structure, example use cases, signal interpretation, and alternative routing. The most important information is front-loadedaisd the 'AUTHORITATIVE' opener and the transaction-code explanations are compact and high-signal.

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, the description carries the burden of explaining return values, and it does so thoroughly: reporting owner, role, transaction code, shares, price, acquired/disposed, and post-transaction holdings. It also covers input alternativeschers, use cases, and the sibling for raw filings, making it complete for an agent to select and invoke correctly.

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 the schema already documents all parameters thoroughly. The description adds useful context about aliases and requiredness, but this is largely redundant with the schema. It does not materially deepen understanding of parameter semantics beyond what the schema provides.

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?

The description clearly identifies the tool as returning parsed SEC Form 3/4/5 insider transaction activity for a US public company, specifying who traded, direction, price, and resulting holdings. It distinguishes itself from raw-filing tools by emphasizing 'parsed into structured transactions' and by implying it is the authoritative source for this specific data.

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?

It explicitly provides example queries ('insider buying at $TICKER', 'did executives sell recently') and points to the alternative tool for raw filing lists: 'For the raw filing list use edgar_company_filings with form_type:"4".' This gives an agent clear when-to-use and when-to-use-other guidance.

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

All Edgar toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources