TickerDB

get_insider_trades

Read-only

One insider's disclosed transactions (SEC Form 4), ordered by disclosure time: the event series of a copy/inverse insider model. Get the slug from get_insiders first. Two rules for backtests: act at disclosed_at (when it became public), never trade_date (up to lag_days earlier; using it is look-ahead); and only open-market trades are decisions: set open_market_only=true to drop grants, option exercises, tax withholding and gifts, and consider exclude_planned=true (pre-scheduled Rule 10b5-1 sales carry little signal; nearly all of Jeff Bezos's Amazon sales are planned). Each trade has ticker (as of disclosure), side, shares, price, value, shares_owned_after, planned, late and an sec_url. Join to get_ohlcv for prices.

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": {
      "insider": "<insider>"
    },
    "name": "get_insider_trades"
  }
}

Input Schema

Name	Required	Description
`end`	No	Last disclosure date YYYY-MM-DD (default: today).
`limit`	No	Rows per page, default 100, max 1000.
`order`	No	desc (default, newest first) or asc.
`start`	No	First disclosure date YYYY-MM-DD (default: start of the plan's history).
`offset`	No	Paging offset, default 0.
`ticker`	No	Only transactions in this company, e.g. "AMZN".
`insider`	Yes	Insider slug from get_insiders, e.g. "jeffrey-p-bezos".
`exclude_planned`	No	true: drop pre-planned Rule 10b5-1 trades.
`open_market_only`	No	true: only open-market purchases and sales (P/S).

Output Schema

Name	Required	Description	Default
`data`	No	The TickerDB API response payload for this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the read-only/safe profile, yet the description still adds substantial domain behavior beyond them: the look-ahead trap in trade_date, what open_market_only excludes (grants, option exercises, tax withholding, gifts), and the weak signal in pre-scheduled 10b5-1 sales. It also discloses response shape (ticker as of disclosure, late, sec_url) and the join path to get_ohlcv.

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?

Front-loaded with the resource identity and the required prerequisite, then the two rules — dense and mostly waste-free. The Bezos parenthetical is illustrative rather than essential, and the field listing at the end slightly duplicates the output schema, but nothing is confusing.

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?

An output schema exists so return values needn't be spelled out, yet the description still flags the semantically loaded fields (planned, late, ticker as of disclosure). With 9 params all documented in the schema and every filter's purpose explained, an agent has everything needed to call this correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description earns above it by explaining the intent behind open_market_only (drops grants, option exercises, tax withholding, gifts) and exclude_planned (pre-scheduled 10b5-1 sales), which the schema only states tersely. Paging and date params are left to the schema, which handles them adequately.

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?

States a specific verb and resource — one insider's disclosed SEC Form 4 transactions, ordered by disclosure time — and frames the dataset's role (event series of a copy/inverse insider model). Clearly distinct from the sibling get_insiders, which supplies the slug this tool consumes.

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?

Explicit prerequisites ('Get the slug from get_insiders first'), explicit backtest rules (act at disclosed_at, never trade_date due to lag_days look-ahead), and explicit filter guidance (open_market_only=true, consider exclude_planned=true) with the reason each matters. No inference required.

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

All TickerDB tools Inspect

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.