Skip to main content
Glama
Prem07a
by Prem07a

dcf_valuation

Estimate intrinsic value per share and margin of safety for a stock using forward DCF with your growth, discount-rate, and terminal-growth assumptions. If growth is not supplied, it uses historical revenue CAGR.

Instructions

Forward DCF: given growth/discount-rate assumptions, estimate intrinsic value per share and the margin of safety vs the current price. Same two-stage model as reverse_dcf (5Y explicit growth + Gordon-growth terminal value), run in the direct rather than solved-for direction. If growth isn't supplied, defaults to the company's own historical revenue CAGR -- a stated assumption, not a prediction; consider cross-checking with reverse_dcf to see what growth the current price already implies.

:param symbol: ticker symbol, e.g. "RELIANCE", "TCS.NS", or "TCS.BO"
:param growth: annual FCF growth assumption, e.g. 0.10 for 10%; defaults to historical revenue CAGR
:param wacc: discount rate assumption (default 0.12 = 12%)
:param terminal_growth: perpetuity growth assumption (default 0.04 = 4%); must be < wacc

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waccNo
growthNo
symbolYes
terminal_growthNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoSet if FCF is negative/zero, shares_outstanding is unavailable, or wacc <= terminal_growth
symbolYes
wacc_pctYesDiscount rate assumption used (input, not derived)
growth_pctYesGrowth-rate assumption used (input, defaulted from history if not supplied)
current_priceNo
projection_yearsNo
shares_outstandingNo
terminal_growth_pctYesPerpetuity growth assumption used (input, not derived)
margin_of_safety_pctNo(intrinsic - current) / current * 100. Positive = the model thinks it's undervalued at the given assumptions.
currency_mismatch_warningNoSet when Yahoo's market-data and financial-statement currencies disagree for this ticker -- this entire valuation becomes unreliable when set.
intrinsic_value_per_shareNo
growth_pct_is_assumed_defaultYesTrue if growth_pct was defaulted from historical revenue CAGR rather than supplied by the caller
Install Server

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so well. It discloses the model structure (5Y explicit growth + Gordon-growth terminal value), the default growth behavior, the 'stated assumption, not a prediction' caveat, and the terminal_growth < wacc constraint. These are meaningful behavioral traits beyond the raw schema.

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 front-loaded with the primary purpose, then provides model context, defaults, cross-check guidance, and parameter documentation in a logical order. Every sentence adds value; even the caveat about historical CAGR earning its place by preventing the agent from mistaking a default for a prediction.

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 DCF tool with four parameters, no annotations, and an output schema present, the description is complete. It covers what the model assumes, how defaults behave, the key constraint, and how the tool differs from reverse_dcf. Nothing critical for choosing or invoking this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the description provides explicit :param documentation for all four parameters. It explains symbol format with examples, growth format and default, wacc default, and terminal_growth default plus the critical constraint that it must be less than wacc. This fully compensates for the missing schema descriptions.

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: 'Forward DCF: given growth/discount-rate assumptions, estimate intrinsic value per share and the margin of safety vs the current price.' It also explicitly contrasts itself with reverse_dcf by noting it runs the same two-stage model 'in the direct rather than solved-for direction,' which clearly distinguishes it from a very similar sibling.

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 positions this tool as the forward/direct DCF variant and points to reverse_dcf as the alternative for reverse-solved growth. It also advises cross-checking with reverse_dcf to see what growth the current price implies, giving an agent concrete guidance on when to use this tool versus a sibling.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Prem07a/FinMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server