Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Insider Transactions

get_insider_transactions

Read-onlyIdempotent

Form 3 / 4 / 5 / 144 line items for a US public company. Returns each transaction (or initial holding / proposed sale) with the insider's name, role, transaction code, share count, price, and notional. Filters by lookback window, transaction code (P=purchase, S=sale, A=grant, M=option exercise, F=tax withholding, etc.), insider role, and minimum share threshold. Institutional tier only — sample / sp500 / pro return ENTITLEMENT_DENIED with an upgrade link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum rows to return. Default 100, max 500.
`ticker`	Yes	Stock ticker symbol, e.g. AAPL, MSFT, BRK.B — or a CIK (SEC identifier), e.g. '0000320193'.
`roles_in`	No	Insider roles to keep. Omit to include any role.
`as_of_date`	No	Point-in-time date (YYYY-MM-DD). Only returns transactions with accepted_at <= this date — eliminates look-ahead bias. When set, lookback_days is ignored.
`min_shares`	No	Minimum \|shares\| per transaction. Omit for no floor.
`lookback_days`	No	How many days back from today to scan transactions for. Ignored when as_of_date is set.
`lineage_detail`	No	Per-row provenance envelope. 'compact' (default) returns source_filing + source_url. 'full' adds accepted_at. 'off' omits lineage.	compact
`transaction_codes`	No	SEC transaction codes to keep (uppercase, single-letter): P=purchase, S=sale, A=grant, M=option exercise, F=tax withholding, G=gift, J=other. Unknown codes are rejected. Omit to include all codes.

Output Schema

TableJSON Schema

Name	Required	Description
`cik`	Yes
`rows`	Yes
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`ticker`	Yes
`company_name`	Yes
`data_age_days`	Yes
`staleness_warning`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / properties / _meta / properties / fundamentals_as_of / description

Previous value: -"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to."New value: +"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt in bulk. Use THIS — not `last_updated` — when telling a user how current the cross-sectional fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to. It is a floor for a single filer, not a ceiling: a filer with a live partition receives its filing, facts and ratios intraday (minutes after EDGAR dissemination), so an entity-scoped read may carry a filing newer than this; cross-sectional ranks (factor scores, earnings signals) refresh with the weekly bulk export."

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / ticker / description

Previous value: -"Stock ticker symbol, e.g. AAPL, MSFT, BRK.B"New value: +"Stock ticker symbol, e.g. AAPL, MSFT, BRK.B — or a CIK (SEC identifier), e.g. '0000320193'."

changedInput schema / properties / ticker / pattern

Previous value: -"^[A-Za-z.\\-]+$"New value: +"^[A-Za-z0-9.\\-]+$"

Changed2 schema fields changedJul 25, 2026

addedOutput schema / properties / _meta / properties / fundamentals_as_of

Added value: +{
+  "description": "ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to.",
+  "type": "string"
+}

addedOutput schema / properties / _meta / properties / price_as_of

Added value: +{
+  "description": "ISO timestamp when the price surfaces were last refreshed.",
+  "type": "string"
+}

Changed2 schema fields changedJul 7, 2026

addedOutput schema / properties / _meta / properties / cost_usd

Added value: +{
+  "additionalProperties": false,
+  "description": "Per-call cost transparency. Omitted for subscription-only tools that have no PAYG-equivalent price.",
+  "properties": {
+    "amount_usd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "basis": {
+      "description": "payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed.",
+      "enum": [
+        "payg_charge",
+        "payg_rate_card"
+      ],
+      "type": "string"
+    },
+    "billed": {
+      "description": "true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "amount_usd",
+    "billed",
+    "basis"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / _meta / properties / latency_ms

Added value: +{
+  "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
+  "minimum": 0,
+  "type": "integer"
+}

Changed4 schema fields changedJun 19, 2026

changedInput schema / properties / transaction_codes / description

Previous value: -"SEC transaction codes to keep (uppercase, single-letter):  P=purchase, S=sale, A=grant, M=option exercise, F=tax withholding, G=gift, J=other.  Omit to include all codes."New value: +"SEC transaction codes to keep (uppercase, single-letter):  P=purchase, S=sale, A=grant, M=option exercise, F=tax withholding, G=gift, J=other.  Unknown codes are rejected.  Omit to include all codes."

addedInput schema / properties / transaction_codes / items / enum

Added value: +[
+  "P",
+  "S",
+  "A",
+  "M",
+  "F",
+  "G",
+  "J"
+]

removedInput schema / properties / transaction_codes / items / maxLength
```
Removed value: -2
```
removedInput schema / properties / transaction_codes / items / minLength
```
Removed value: -1
```

Changed1 schema field changedJun 18, 2026
- addedOutput schema / properties / _meta / properties / pit_safe / description
```
Added value: +"true iff a zero-look-ahead point-in-time cut was applied to every returned figure"
```
Changed1 schema field changedJun 5, 2026
- changedOutput schema / properties / rows / items / properties / shares / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
AddedMay 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds meaningful behavioral context by stating the entitlement requirement (institutional tier only, with ENTITLEMENT_DENIED for lower tiers), which is an auth/access condition not present in annotations. It also clarifies the nature of the returned data (line items with insider details). No contradictions with 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 three sentences with zero redundancy. It front-loads the core purpose, then lists filters and the key entitlement caveat. Every sentence earns its place, and no important information is buried or padded.

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?

Given the rich input schema (all 8 parameters described, 100% coverage) and the existence of an output schema, the description covers the essential purpose, filters, and entitlement behavior. It does not explain error cases (e.g., invalid ticker) or rate limits, but those are minor given the structured schema. The description is complete enough for an agent to call the tool 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 baseline is 3. The description mostly restates what the schema already says: filters by lookback, transaction code, insider role, and minimum share threshold, and it gives the same code meanings (P, S, A, etc.) already in the schema's enum descriptions. It adds little beyond the schema, so a 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 starts with a specific verb and resource: 'Form 3 / 4 / 5 / 144 line items for a US public company.' It enumerates the returned fields and filter dimensions, and the subject matter (insider transactions) clearly distinguishes it from sibling tools like get_insider_sentiment or get_institutional_holdings. An agent can immediately understand what this tool does and how it differs from alternatives.

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

Usage Guidelines3/5

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

The description provides clear context about the institutional tier restriction ('sample / sp500 / pro return ENTITLEMENT_DENIED') and describes the filtering capabilities, but it never explicitly says when to prefer this tool over sibling tools such as get_insider_sentiment or get_sec_filing_links. Usage is implied through purpose clarity rather than stated as explicit when/when-not guidance, so it does not meet the bar for a 4.

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

All Valuein — SEC EDGAR Fundamentals & Smart-Money Data 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.