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

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

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 changedOct 29, 2026

addedOutput schema / properties / rows / items / properties / metrics_display

Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "description": "This row's shares, price and values rendered for prose ('1.28M shares', '$249.17', '$318.92M'). QUOTE THESE VERBATIM instead of the raw numbers.",
+  "type": "object"
+}

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description

Previous value: -"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."New value: +"payg_charge = real pay-per-call charge (a card or MPP payment through agent-pay). payg_rate_card = indicative price, not billed."

Changed2 schema fields changedOct 29, 2026

changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description

Previous value: -"payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed."New value: +"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."

changedOutput schema / properties / _meta / properties / cost_usd / properties / billed / description

Previous value: -"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free."New value: +"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value only: no charge was made for this call (it was within your plan)."

AddedOct 16, 2026
RemovedSep 29, 2026

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

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the description correctly spends its words elsewhere: the entitlement failure mode and its error code, the exact row payload, and the as_of_date vs lookback_days precedence. That is real behavioral context beyond structured fields, though rate limits, pagination, and empty-result behavior are unmentioned.

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?

Three dense sentences, front-loaded with what is returned before the filter list and the entitlement caveat. The middle sentence listing filters largely duplicates the schema and could be trimmed, but nothing is padded or vague.

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 an 8-parameter read tool with an output schema and full annotation coverage, the description supplies the payload shape, the entitlement constraint, and the as_of_date/lookback interaction — enough to call it correctly. The one gap is guidance on choosing between this and the related insider/holder tools.

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 ticker/CIK, limit, roles_in, as_of_date, min_shares, lookback_days, lineage_detail, and transaction_codes. The description restates the filter set and repeats the code legend (P/S/A/M/F) that the schema already provides, adding no syntax or edge-case detail beyond it — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and its source documents ('Form 3 / 4 / 5 / 144 line items for a US public company') and enumerates the per-row fields returned, so the agent knows exactly what it retrieves. It does not explicitly contrast itself with adjacent siblings such as get_insider_sentiment, get_top_holders, or get_blockholders, so it stops short of a 5.

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 tier note ('Institutional tier only — sample / sp500 / pro return ENTITLEMENT_DENIED') is genuinely useful usage context, but it is about access, not selection. There is no statement of when to reach for this tool versus get_insider_sentiment or get_institutional_holdings, and no exclusions beyond the entitlement gate, so usage is implied rather than guided.

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.