FilingDelta

Insider trades card (paid $0.05)

get_insider

Read-onlyIdempotent

Paid $0.05 USDC on Base. Call when you need what a company's officers and directors filed on SEC Form 4 and 4/A in the last 30 days: each trade graded high, medium or low by the FilingDelta rubric (not SEC grading), with figures and an EDGAR XML citation. Free sample over HTTP: /sample/insider/{ticker}. Tickers: NVDA. Others return 404 (no charge).

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_insider"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Ticker

Output Schema

Name	Required	Description	Default
`period`	No
`ticker`	Yes
`changes`	Yes
`company`	No
`accession`	No
`period_end`	No
`source_url`	Yes
`filing_date`	No
`filing_type`	Yes
`generated_at`	No
`comparison_basis`	No
`high_materiality_count`	No
`new_material_items_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world traits, yet the description still adds the price ($0.05 USDC on Base), the billing consequence of a 404 (no charge), the source of the grading (FilingDelta rubric, explicitly not SEC grading), and citation behavior. That is substantial value beyond the structured fields, with no contradiction.

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?

Cost, use condition, data definition, grading caveat, sample URL and ticker restriction are all packed into four front-loaded sentences with no filler. Minor redundancy between title price and body price, but nothing wasteful.

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?

For a paid, single-parameter tool with an output schema, everything an agent needs is present: price, trigger condition, data scope, grading provenance, free sample path, and failure behavior for unsupported tickers. Nothing material is missing.

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% and the single parameter is enum-constrained, so the baseline is 3. The description still adds meaning the schema cannot express: which ticker currently works and that any other value returns 404 at no cost.

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 resource (SEC Form 4 and 4/A filings by officers and directors), a concrete time window (last 30 days), and the added value (FilingDelta rubric grading with EDGAR XML citation). An agent can distinguish this from sibling data tools without opening the schema.

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?

"Call when you need..." gives an explicit use condition, and the ticker constraint plus the free sample endpoint give practical routing context. It stops short of naming an alternative tool or stating when not to call it, so it is clear but not exhaustive.

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

All FilingDelta 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.

Resources

Need Help?