Skip to main content
Glama

BRAINIAC Equity Analytics

Two-stage discounted cash flow

equity-analytics_dcf-valuation
Read-onlyIdempotent

Discount explicit free cash flows and a Gordon or exit-multiple terminal value to enterprise and equity value per share, with a discount-rate and growth sensitivity grid. Price $0.04 USDC. POST /api/v1/equity-analytics/dcf-valuation. An unpaid call returns the x402 payment terms and does not run.

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": {
      "fcf": "<fcf>",
      "discountRate": "<discountRate>",
      "terminal": "<terminal>",
      "sharesOutstanding": "<sharesOutstanding>"
    },
    "name": "equity-analytics_dcf-valuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
fcfYesfcf, array. Required.
midYearNomidYear, boolean. Required.
netDebtNonetDebt, number. Required.
terminalYesterminal, object. Required.
discountRateYesdiscountRate, number. Required.
sharesOutstandingYessharesOutstanding, number. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
perShareNoperShare. Number.
pvExplicitNopvExplicit. Number.
pvTerminalNopvTerminal. Number.
equityValueNoequityValue. Number.
limitationsNolimitations. Array.
sensitivityNosensitivity. Array.
terminalValueNoterminalValue. Number.
enterpriseValueNoenterpriseValue. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds material behavior beyond that: a hard price of $0.04 USDC, a POST endpoint, and the crucial detail that an unpaid call short-circuits and returns x402 payment terms without executing. It does not discuss rate limits, partial failures, or validation behavior.

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?

Three short sentences, front-loaded with the computational purpose and followed by payment and transport details; every sentence carries distinct information. The endpoint path is somewhat mechanical but is needed for the HTTP call, so it earns its place.

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

Completeness4/5

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

An output schema exists, so return-value explanation is not required, and the description covers the payment handshake that would otherwise be the biggest surprise for an agent. What remains thin is the interpretation of the fcf array and the midYear/netDebt conventions for a nested six-parameter financial model.

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 schema already documents all six parameters and the nested terminal object. The description adds conceptual meaning by naming the two terminal-value methods and noting that discount rate and growth are swept in a sensitivity grid, but it does not clarify fcf period semantics, midYear convention, or netDebt sign handling beyond what the schema states.

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?

The description gives a specific verb and resource: discount explicit FCFs plus a Gordon or exit-multiple terminal value into enterprise and equity value per share, plus a sensitivity grid. That is far more informative than the title alone. It does not differentiate itself from the related sibling equity-analytics_wacc-calculate, which an agent might otherwise consider for the discount-rate input.

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

Usage Guidelines3/5

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

Usage is implied by the valuation framing and the stated required inputs, but there is no explicit when-to-use/when-not-to-use guidance and no mention of the sibling WACC calculator that naturally produces the discountRate argument. The payment guidance ('An unpaid call returns the x402 payment terms and does not run') is the one genuinely operational instruction provided.

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