Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Compute M&A Accretion/Dilution

compute_accretion_dilution

Read-onlyIdempotent

M&A accretion/dilution: the standard sell-side/banker quick-screen for whether a proposed acquisition adds to (accretive) or subtracts from (dilutive) the acquirer's EPS in the first pro-forma year. Pulls net income + shares outstanding for both companies, and each side's latest EOD close (acquirer's price converts stock consideration into new shares issued; target's price is used only to disclose the offer premium). Caller sets the consideration mix (cash_pct, cash-financed by new debt or the acquirer's balance sheet), annual run-rate synergies, and the new-debt interest rate. A SINGLE pro-forma-year bridge — NOT a multi-year merger model; synergy ramp, integration costs, and purchase-price-allocation amortization (goodwill/intangibles step-up) are not modeled (see result.caveats[]). result.accretion_dilution_pct positive = accretive, negative = dilutive. Tier: sp500+.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cash_pct`	Yes	Fraction (0-1) of deal value paid in cash; the remainder (1 - cash_pct) is paid in acquirer stock.
`tax_rate`	No	Effective tax rate applied to synergies and the interest drag. Default 0.21.
`as_of_date`	No	Point-in-time cutoff (YYYY-MM-DD) for both companies' fundamentals + prices. Omit to use the latest knowable data.
`target_ticker`	Yes	Target's stock ticker symbol, e.g. ATVI.
`acquirer_ticker`	Yes	Acquirer's stock ticker symbol, e.g. MSFT.
`synergies_pretax`	No	Pretax annual run-rate cost/revenue synergies (USD). Default 0.
`cash_financing_source`	No	Where the cash consideration is funded from. "new_debt" (default) applies an after-tax interest drag; "balance_sheet_cash" applies none.	new_debt
`offer_price_per_share`	Yes	Offer price per target share (USD).
`new_debt_interest_rate`	No	Annual interest rate on new acquisition debt (only used when cash_financing_source is "new_debt"). Default 0.06.
`target_share_price_override`	No	Override the target's live EOD close (used only for the disclosed premium). Leave unset to use the latest R2-derived price.
`acquirer_share_price_override`	No	Override the acquirer's live EOD close. Leave unset to use the latest R2-derived price.

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.

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.7/5.0

Behavior5/5

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

With readOnlyHint/idempotentHint already covering safety, the description adds meaningful behavior: it pulls net income, shares outstanding, and EOD closes; explains how acquirer price is used to issue new shares and target price only for premium disclosure; and warns that synergy ramp, integration costs, and PPA amortization are excluded, directing agents to result.caveats[].

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 dense but every sentence earns its place: purpose is front-loaded, key inputs are mentioned, and caveats/output semantics are at the end. The formatting uses clear emphasis ('A SINGLE pro-forma-year bridge') to separate scope from mechanics.

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 an 11-parameter tool with an output schema, the description covers what data is fetched, what the caller must set, what is deliberately not modeled, and how to interpret result.accretion_dilution_pct. It also points to result.caveats[] for remaining unknowns, making it complete enough to call 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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining how cash_pct/cash_financing_source form the consideration mix, describing synergies as annual run-rate, and clarifying the distinct roles of acquirer vs target share prices.

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 opening sentence names a specific verb ('compute') and resource ('M&A accretion/dilution') and defines the metric in plain terms. It further distinguishes itself from multi-year models by stating it is a single pro-forma-year bridge, so an agent can separate it from compute_dcf/compute_lbo siblings.

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?

It clearly states when to use this tool: as a standard sell-side/banker quick-screen for first-year EPS impact. It also gives an explicit exclusion ('NOT a multi-year merger model') and lists omitted items, but it never names a specific alternative tool to use for the multi-year case, so it stops short of the 5-level guidance.

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.