Skip to main content
Glama

dcf_wacc_valuation

Read-onlyIdempotent

[Deterministic corporate valuation engine. Pure calculation, read-only, side-effect free]. Discounted Cash Flow (DCF) enterprise valuation model: Capital Asset Pricing Model (CAPM) Cost of Equity, after-tax Cost of Debt, blended Weighted Average Cost of Capital (WACC), Gordon Growth perpetual terminal value, net debt bridge waterfall, and multi-parameter sensitivity matrix. Usage: Use this tool to calculate intrinsic Enterprise Value, Equity Value, and implied share price from forecast cash flows. Do NOT use for solvency default prediction (use 'corporate_default_predictor') or accounting anomaly forensics (use 'financial_trend_anomaly'). Returns: JSON object with { enterpriseValue: number, equityValue: number, impliedSharePrice: number | null, wacc: number, costOfEquity: number, costOfDebtAfterTax: number, pvForecastFlows: number, terminalValue: number, sensitivityMatrix: Array<{ wacc, terminalGrowth, enterpriseValue }> }.

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": {
      "waccParams": "<waccParams>",
      "forecastCashFlows": "<forecastCashFlows>",
      "terminalGrowthRate": "<terminalGrowthRate>"
    },
    "name": "dcf_wacc_valuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoReporting currency code (default EUR)EUR
waccParamsYesWACC cost of capital inputs
netDebtBridgeNoBalance sheet net debt bridge to calculate Equity Value
forecastCashFlowsYesAt least 2 projection periods of forecast FCFF
sharesOutstandingNoTotal diluted shares for implied share price calculation
midYearDiscountingNoWhether to apply mid-year discounting (period - 0.5)
terminalGrowthRateYesPerpetual growth rate g (e.g. 0.02 for 2.0%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the 'pure calculation, side-effect free' framing is partly redundant; however, 'deterministic' adds a meaningful guarantee about reproducibility. The description also compensates for the absent output schema by enumerating the exact return fields, which is genuine behavioral context. It does not mention domain preconditions (e.g. terminal growth must be below WACC) or error behavior, keeping it short of a 5.

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?

Front-loaded with a bracketed summary, then clearly separated 'Usage:' and 'Returns:' blocks, so an agent can skim to the routing decision. The formula enumeration in the first sentence is dense but each item maps to a computed output, so it earns its place; the structure is slightly over-packed but not 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 7-parameter tool with nested objects and no output schema, the definition covers purpose, routing, and the full return shape including nullability of impliedSharePrice and the sensitivity matrix structure. Nothing an agent needs in order to select and invoke it correctly is 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 every nested field carries its own example and unit convention (e.g. beta 1.15, taxRate 0.24), so the schema does the heavy lifting. The description names the conceptual inputs (CAPM, after-tax cost of debt, net debt bridge) but adds no format, unit, or constraint detail beyond what the schema already documents. Baseline 3 applies.

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 verb and resource ('Discounted Cash Flow (DCF) enterprise valuation model') and enumerates the exact components computed (CAPM cost of equity, after-tax cost of debt, WACC, Gordon Growth terminal value, net debt bridge, sensitivity matrix). It explicitly contrasts itself with two named siblings, so an agent can distinguish it 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 Guidelines5/5

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

Provides an explicit 'Usage:' line stating the input/output intent (intrinsic Enterprise Value, Equity Value, implied share price from forecast cash flows) and an explicit 'Do NOT use for' clause routing solvency work to 'corporate_default_predictor' and forensics to 'financial_trend_anomaly'. Both when-to-use and when-not-to-use are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources