Skip to main content
Glama

insidergraph

by com.insidergraph
OverviewDiscussionsAdmin

Insider trades before bad news

trades_before_events
Read-onlyIdempotent

Cross-feed signal: for issuers that filed a material 8-K event, show SEC Form 4 insider transactions in the N days BEFORE the event - e.g. insider selling before a bankruptcy, restatement, or delisting. Joins two feeds through the shared entity graph; raw EDGAR cannot answer this in one query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows, default 50, cap 500.
sinceNoEarliest event date, YYYY-MM-DD.
txn_typeNoInsider transaction filter: sell (default - selling before bad news), buy, or all.sell
item_codesNo8-K items to anchor on, e.g. ["1.03","4.02","3.01"]. Default: distress items 1.03, 2.06, 3.01, 4.02.
days_beforeNoLookback window before the event date, default 60.
min_value_usdNoMinimum insider transaction value in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / item_codes / default
      Added value: +[
+  "1.03",
+  "2.06",
+  "3.01",
+  "4.02"
+]
    • addedInput schema / properties / item_codes / items / enum
      Added value: +[
+  "1.01",
+  "1.02",
+  "1.03",
+  "1.04",
+  "1.05",
+  "2.01",
+  "2.02",
+  "2.03",
+  "2.04",
+  "2.05",
+  "2.06",
+  "3.01",
+  "3.02",
+  "3.03",
+  "4.01",
+  "4.02",
+  "5.01",
+  "5.02",
+  "5.03",
+  "5.04",
+  "5.05",
+  "5.06",
+  "5.07",
+  "5.08",
+  "6.01",
+  "6.02",
+  "6.03",
+  "6.04",
+  "6.05",
+  "7.01",
+  "8.01",
+  "9.01"
+]
    • addedInput schema / properties / txn_type / default
      Added value: +"sell"
  2. Changed4 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / days_before / default
      Added value: +60
    • addedInput schema / properties / limit / default
      Added value: +50
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to restate safety. It adds useful behavioral context beyond annotations: the tool joins two feeds through the shared entity graph and performs a temporal before-event lookup. This is transparent about the underlying mechanism without contradicting 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?

The description is two sentences with no filler. The main purpose and unique value proposition are front-loaded in the first sentence, and the second sentence clarifies why this tool is distinct from a raw EDGAR query. Every part earns its place.

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?

For a cross-feed query tool with no output schema, the description explains the core behavior and the key limitation (raw EDGAR cannot answer it). It could mention return shape or coverage dependencies, but for selection and invocation the schema and annotations cover the necessary details. Slight gap regarding output expectations keeps it from a 5.

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?

The schema provides 100% description coverage for all six parameters, so the description does not need to explain each parameter. It does reinforce the meaning of key concepts like 'N days BEFORE' and 'material 8-K event', but adds no semantic detail beyond what the schema already provides. Baseline 3 is appropriate.

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 states a specific verb ('show') and resource (SEC Form 4 insider transactions before material 8-K events), with concrete examples like bankruptcy, restatement, and delisting. It also clearly distinguishes itself from sibling tools by emphasizing the cross-feed join that raw EDGAR cannot answer in one query.

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

Usage Guidelines4/5

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

The description gives clear context for when to use this tool: when the user needs insider transactions occurring shortly before a company files a material 8-K event. It does not explicitly name alternatives or state when not to use it, but the cross-feed framing and siblings list make the intended use fairly evident.

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

All insidergraph 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