Skip to main content
Glama

NovaPixel LexGrid

dcf_wacc_valuation

Discounted Cash Flow (DCF) enterprise valuation engine: CAPM Cost of Equity, after-tax Cost of Debt, blended WACC, Gordon Growth terminal value, net debt bridge waterfall, and multi-parameter sensitivity matrix.

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
waccParamsYes
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

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the calculation pipeline (CAPM, WACC, Gordon Growth, net debt bridge, sensitivity), but does not state key assumptions or constraints such as Gordon Growth g < WACC, handling of missing weights, currency behavior, or what the engine returns.

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?

Single dense sentence front-loads DCF valuation and lists components efficiently. It is readable, though the long clause chain could be more structured for scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 7-parameter nested valuation engine with no annotations and no output schema, the description is too thin. It does not explain return values (enterprise value, equity value, implied share price, WACC/sensitivity outputs) or calculation assumptions, which an agent needs to invoke it confidently.

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 86%, so the parameters are already well documented. The description adds no parameter-level meaning beyond naming the financial components, so it neither compensates nor detracts.

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?

Names DCF enterprise valuation and enumerates the exact computations: CAPM cost of equity, after-tax cost of debt, WACC, Gordon Growth terminal value, net-debt bridge, and sensitivity matrix. An agent can tell this is a valuation engine, though the description does not contrast it with the sibling predictors/calculators.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus corporate_default_predictor, csrd_esg_calculator, or financial_trend_anomaly. It also omits prerequisites such as needing forecast FCFF and WACC inputs, leaving usage to inference from the name.

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