Skip to main content
Glama

Valuation API

calculate_dcf

Read-onlyIdempotent

Compute a Discounted Cash Flow (DCF) valuation: enterprise value from projected free cash flows plus a Gordon-growth terminal value. WHEN TO USE: to value a company or asset from its projected free cash flows, WACC and perpetual terminal growth rate (standard corporate/asset valuation). WHEN NOT TO USE: for a single-exit lump-sum investment (use calculate_irr), or when you need the discount rate itself (use calculate_wacc). BEHAVIOUR: pure deterministic calculation — no side effects, no network or storage access; idempotent and non-destructive. Terminal value uses the Gordon Growth Model; it is only defined when wacc is strictly greater than terminal_growth_rate. RETURNS: JSON object { inputs, results: { present_value, terminal_value, enterprise_value } }, each rounded to 2dp. present_value is the discounted explicit-period FCFs; enterprise_value = present_value + discounted terminal value (debt and cash are NOT netted — this is enterprise value, not equity value). PARAMETERS: free_cash_flows (array of per-period projected free cash flows, typically positive; the first element is discounted by one period), wacc (decimal, e.g. 0.10 = 10% — never pass percentage points; must be > terminal_growth_rate), terminal_growth_rate (decimal perpetual growth rate, e.g. 0.03 = 3% — never pass percentage points; must be < wacc).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waccYesWeighted average cost of capital as a decimal, e.g. 0.10 = 10% (never pass percentage points). Must be strictly greater than terminal_growth_rate.
free_cash_flowsYesProjected free cash flows per period, e.g. [5000000, 6000000, 7000000, 8000000, 9000000]. Typically positive; first element discounted one period.
terminal_growth_rateYesPerpetual terminal growth rate as a decimal, e.g. 0.03 = 3% (never pass percentage points). Must be strictly less than wacc, otherwise terminal value is undefined.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description states 'pure deterministic calculation — no side effects, no network or storage access; idempotent and non-destructive,' reinforcing the readOnlyHint and idempotentHint annotations. It also discloses the Gordon Growth Model constraint (wacc > terminal_growth_rate) and clarifies that debt and cash are not netted, adding meaningful behavioral context beyond the annotations.

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 longer and structured with uppercase section headers, but every sentence carries substantive guidance: purpose, when to use/not use, behavior, return shape, and param semantics. It is front-loaded with the core purpose and not padded.

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?

This is a complex financial tool with three required parameters and no output schema, yet the description fully covers return structure, rounding, the mathematical constraint, and the distinction between enterprise and equity value. Combined with annotations, the agent has everything needed to invoke and interpret the result correctly.

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 baseline is 3. The description's PARAMETERS section largely restates the schema: decimals not percentages, first FCF discounted one period, and the wacc/growth constraint. It adds no new meaning beyond what the schema already provides, so it stays at the baseline.

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 description opens with a specific verb and resource: 'Compute a Discounted Cash Flow (DCF) valuation: enterprise value from projected free cash flows plus a Gordon-growth terminal value.' It clearly distinguishes itself from siblings by naming calculate_irr and calculate_wacc as alternatives for different cases. The purpose is unambiguous and action-oriented.

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?

The description explicitly provides 'WHEN TO USE' and 'WHEN NOT TO USE' sections with named alternative tools: calculate_irr for single-exit lump-sum investments and calculate_wacc for discount-rate needs. This gives the agent direct routing instructions, leaving nothing to inference.

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.

TDQS

A4.6/5.0
Disambiguation4/5

Most tools map cleanly to distinct valuation concepts (CAPM, WACC, DCF, multiples, NPV/IRR/MOIC, beta adjustment), so an agent can generally select correctly. The main ambiguity is that calculate_irr already includes MOIC and an IRR sensitivity table, making irr_sensitivity and calculate_moic partially overlapping in purpose despite their clarifications.

Naming Consistency4/5

The overwhelming pattern is calculate_<metric>, with clear snake_case and a consistent prefix throughout. The one outlier is irr_sensitivity, which drops the calculate_ prefix and breaks the established verb_noun convention.

Tool Count5/5

Twelve tools is a well-scoped size for a valuation calculation API, covering cost of capital, DCF, multiples, and return metrics without bloat. Each tool represents a meaningful standalone calculation an agent would need.

Completeness4/5

The core valuation workflow is well covered: cost of equity, WACC, DCF, enterprise value, multiples, and investment return metrics are all present. The notable gap is the reverse of calculate_enterprise_value—deriving equity value from enterprise value—and there is no standalone terminal value calculator, though both are workable gaps.