Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Merger accretion and dilution

compute_accretion_dilution

Read-onlyIdempotent

Returns whether a proposed acquisition raises or lowers the acquirer's earnings per share in the first year after the deal, with deal value, new shares and debt, pro forma net income, shares and EPS, and the takeover premium, from both companies' latest annual 10-K figures and month-end closing prices. Use this when the user asks whether a deal would be accretive or dilutive at an offer price, cash and stock mix and synergies they choose. It covers one year only: synergy ramp, integration costs and purchase accounting are not modelled.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cash_pct`	Yes	Share of the deal value settled in cash, 0 to 1; the rest is acquirer stock, e.g. 0.5.
`tax_rate`	No	Tax rate on synergies and interest, 0 to 1; defaults to 0.21, e.g. 0.25.
`as_of_date`	No	Point-in-time cutoff for both companies, YYYY-MM-DD: filings accepted and closes on or before this date, e.g. 2024-06-30.
`target_ticker`	Yes	Ticker symbol or SEC CIK of the company being acquired, e.g. AAPL.
`acquirer_ticker`	Yes	Ticker symbol or SEC CIK of the acquiring company, e.g. MSFT.
`synergies_pretax`	No	Yearly pretax synergies in USD at full run rate; defaults to 0, e.g. 500000000.
`cash_financing_source`	No	How the cash is funded: new_debt (default, adds after-tax interest) or balance_sheet_cash (no interest cost), e.g. balance_sheet_cash.	new_debt
`offer_price_per_share`	Yes	Price offered per target share in USD, above zero, e.g. 250.
`new_debt_interest_rate`	No	Interest rate on new acquisition debt, 0 to 0.5, used with new_debt; defaults to 0.06, e.g. 0.07.
`target_share_price_override`	No	Target share price in USD used instead of its month-end close, for the takeover premium only, e.g. 180.
`acquirer_share_price_override`	No	Acquirer share price in USD used instead of its month-end close, e.g. 420.

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`result`	Yes
`target_ticker`	Yes
`acquirer_ticker`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedSep 29, 2026

changedInput schema / properties / acquirer_share_price_override / description

Previous value: -"Override the acquirer's live EOD close. Leave unset to use the latest R2-derived price."New value: +"Acquirer share price in USD used instead of its month-end close, e.g. 420."

changedInput schema / properties / acquirer_ticker / description

Previous value: -"Acquirer's stock ticker symbol, e.g. MSFT."New value: +"Ticker symbol or SEC CIK of the acquiring company, e.g. MSFT."

changedInput schema / properties / as_of_date / description

Previous value: -"Point-in-time cutoff (YYYY-MM-DD) for both companies' fundamentals + prices. Omit to use the latest knowable data."New value: +"Point-in-time cutoff for both companies, YYYY-MM-DD: filings accepted and closes on or before this date, e.g. 2024-06-30."

changedInput schema / properties / cash_financing_source / description

Previous value: -"Where the cash consideration is funded from. \"new_debt\" (default) applies an after-tax interest drag; \"balance_sheet_cash\" applies none."New value: +"How the cash is funded: new_debt (default, adds after-tax interest) or balance_sheet_cash (no interest cost), e.g. balance_sheet_cash."

changedInput schema / properties / cash_pct / description

Previous value: -"Fraction (0-1) of deal value paid in cash; the remainder (1 - cash_pct) is paid in acquirer stock."New value: +"Share of the deal value settled in cash, 0 to 1; the rest is acquirer stock, e.g. 0.5."

changedInput schema / properties / new_debt_interest_rate / description

Previous value: -"Annual interest rate on new acquisition debt (only used when cash_financing_source is \"new_debt\"). Default 0.06."New value: +"Interest rate on new acquisition debt, 0 to 0.5, used with new_debt; defaults to 0.06, e.g. 0.07."

changedInput schema / properties / offer_price_per_share / description

Previous value: -"Offer price per target share (USD)."New value: +"Price offered per target share in USD, above zero, e.g. 250."

changedInput schema / properties / synergies_pretax / description

Previous value: -"Pretax annual run-rate cost/revenue synergies (USD). Default 0."New value: +"Yearly pretax synergies in USD at full run rate; defaults to 0, e.g. 500000000."

changedInput schema / properties / target_share_price_override / description

Previous value: -"Override the target's live EOD close (used only for the disclosed premium). Leave unset to use the latest R2-derived price."New value: +"Target share price in USD used instead of its month-end close, for the takeover premium only, e.g. 180."

changedInput schema / properties / target_ticker / description

Previous value: -"Target's stock ticker symbol, e.g. ATVI."New value: +"Ticker symbol or SEC CIK of the company being acquired, e.g. AAPL."

changedInput schema / properties / tax_rate / description

Previous value: -"Effective tax rate applied to synergies and the interest drag. Default 0.21."New value: +"Tax rate on synergies and interest, 0 to 1; defaults to 0.21, e.g. 0.25."

removedOutput schema / properties / _meta / properties / cost_usd

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

removedOutput schema / properties / _meta / properties / data_plan

Removed value: -{
-  "description": "Access plan: sample | sp500 | pro | full",
-  "type": "string"
-}

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

Previous 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."New value: +"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."

removedOutput schema / properties / _meta / properties / last_updated

Removed value: -{
-  "description": "ISO timestamp when the snapshot was exported",
-  "type": "string"
-}

removedOutput schema / properties / _meta / properties / latency_ms

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

removedOutput schema / properties / _meta / properties / limit_warnings

Removed value: -{
-  "description": "Soft-warning array for partial fulfillment. Each entry carries a stable subcode + remediation.options[]. AI agents pattern-match on subcode.",
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "const": "LIMIT_EXCEEDED",
-        "type": "string"
-      },
-      "current_plan": {
-        "type": "string"
-      },
-      "extensions": {
-        "additionalProperties": {},
-        "type": "object"
-      },
-      "limit_type": {
-        "type": "string"
-      },
-      "limit_value": {},
-      "remediation": {
-        "additionalProperties": true,
-        "properties": {
-          "contact_sales": {
-            "type": "string"
-          },
-          "default_action": {
-            "type": "string"
-          },
-          "options": {
-            "items": {
-              "additionalProperties": {},
-              "type": "object"
-            },
-            "type": "array"
-          },
-          "pricing_page": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "options",
-          "default_action",
-          "pricing_page",
-          "contact_sales"
-        ],
-        "type": "object"
-      },
-      "requested_value": {},
-      "returned_value": {},
-      "subcode": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "code",
-      "subcode",
-      "limit_type",
-      "current_plan",
-      "remediation"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / _meta / properties / payg_override

Removed value: -{
-  "additionalProperties": false,
-  "description": "Set when this single response was paid for via the agent-pay PAYG flow — the rate-limit / depth-limit checks were bypassed for this call only.",
-  "properties": {
-    "amount_cents": {
-      "type": "number"
-    },
-    "entity_scope_hash": {
-      "type": "string"
-    },
-    "meter": {
-      "type": "string"
-    },
-    "quote_id": {
-      "type": "string"
-    },
-    "retry_token_hash": {
-      "type": "string"
-    },
-    "ticker_count": {
-      "type": "number"
-    },
-    "tool": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "quote_id",
-    "tool",
-    "meter",
-    "amount_cents",
-    "ticker_count",
-    "entity_scope_hash",
-    "retry_token_hash"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / _meta / properties / rate_limit

Removed value: -{
-  "additionalProperties": false,
-  "description": "Caller's remaining budget",
-  "properties": {
-    "limit": {
-      "type": "integer"
-    },
-    "remaining": {
-      "type": "integer"
-    },
-    "reset_at": {
-      "description": "ISO 8601 timestamp when the window resets",
-      "type": "string"
-    },
-    "window": {
-      "enum": [
-        "minute",
-        "hour"
-      ],
-      "type": "string"
-    }
-  },
-  "required": [
-    "limit",
-    "remaining",
-    "reset_at",
-    "window"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / _meta / properties / request_id

Removed value: -{
-  "description": "Per-request correlation id (8-char)",
-  "type": "string"
-}

removedOutput schema / properties / _meta / properties / schema_version

Removed value: -{
-  "description": "Parquet schema version from manifest.json",
-  "type": "string"
-}

removedOutput schema / properties / _meta / properties / snapshot

Removed value: -{
-  "description": "Snapshot directory name (e.g. snapshot_20260420)",
-  "type": "string"
-}

removedOutput schema / properties / _meta / properties / truncation / properties / current_plan
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _meta / properties / truncation / properties / upgrade_required_for
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _meta / properties / truncation / properties / upgrade_url
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / _meta / required

Previous value: -[
-  "data_plan",
-  "schema_version",
-  "snapshot",
-  "last_updated",
-  "source",
-  "pit_safe"
-]New value: +[
+  "source",
+  "pit_safe"
+]

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

AddedJul 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, so the bar is lower. The description still adds meaningful context the annotations cannot: data provenance (latest annual 10-K figures and month-end closing prices) and hard modelling boundaries (one-year horizon, no synergy ramp/integration costs/purchase accounting).

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 front-loaded sentences: purpose/outputs, when-to-use, then scope limits. Every sentence earns its place, though the output enumeration overlaps with the existing output schema and is slightly verbose.

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?

With complete schema coverage, an output schema, and annotations covering the safety profile, the description supplies the remaining needed context: what the call computes, its data sources, and its modelling limits. Nothing an agent needs to invoke it correctly appears to be missing.

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% and each of the 11 parameters is documented with units, ranges and examples, so the schema does the heavy lifting. The description only gestures at the inputs (offer price, cash/stock mix, synergies) without adding syntax or format detail beyond what the schema already provides, which is the baseline 3 case.

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?

It names a specific computation (first-year EPS accretion/dilution from a proposed acquisition) and enumerates the outputs produced, which clearly separates it from siblings like compute_dcf and compute_lbo. An agent can identify the tool from the first clause 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?

"Use this when the user asks whether a deal would be accretive or dilutive at an offer price, cash and stock mix and synergies they choose" gives a clear triggering condition, and the closing sentence states an explicit exclusion (one year only; synergy ramp, integration costs and purchase accounting not modelled). It stops short of naming an alternative sibling, so it is not a full 5.

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.