Skip to main content
Glama

BRAINIAC Equity Analytics

Weighted average cost of capital

equity-analytics_wacc-calculate
Read-onlyIdempotent

CAPM cost of equity and after-tax cost of debt combined into WACC from supplied equity and debt values. Price $0.02 USDC. POST /api/v1/equity-analytics/wacc-calculate. 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": {
      "equityValue": "<equityValue>",
      "debtValue": "<debtValue>",
      "riskFree": "<riskFree>",
      "beta": "<beta>",
      "equityRiskPremium": "<equityRiskPremium>",
      "costOfDebt": "<costOfDebt>",
      "taxRate": "<taxRate>"
    },
    "name": "equity-analytics_wacc-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
betaYesriskFree, number. Required.
taxRateYestaxRate, number, from 0 to 1. Required.
riskFreeYesriskFree, number. Required.
debtValueYesdebtValue, number, from 0 to any. Required.
costOfDebtYesriskFree, number. Required.
equityValueYesequityValue, number. Required.
sizePremiumNosizePremium, number. Required.
equityRiskPremiumYesriskFree, number. Required.

Output Schema

NameRequiredDescriptionDefault
waccNowacc. Number.
sourcesNosources. Array.
weightsNoweights. Object.
limitationsNolimitations. Array.
costOfEquityNocostOfEquity. Number.
afterTaxCostOfDebtNoafterTaxCostOfDebt. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description earns credit for adding what annotations cannot express: the $0.02 USDC price point and the crucial x402 behavior that an unpaid call returns payment terms without executing. It does not disclose assumptions of the model (e.g., how sizePremium feeds into cost of equity), which would help the agent interpret results.

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?

Three short sentences with the method statement front-loaded, followed by price, endpoint, and payment-failure behavior. Every sentence carries distinct information; nothing is repeated from the title or annotations.

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?

Because an output schema exists, the description need not explain return values, and it covers cost, transport, and failure mode. The remaining gap is the eight-parameter model itself: sizePremium appears in the schema but not in the description, leaving the agent without guidance on when to supply it.

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, but the schema's own descriptions are low-value boilerplate and several are visibly wrong (beta, costOfDebt, and equityRiskPremium all read 'riskFree, number'). The description adds no parameter-level meaning of its own and does not mention sizePremium at all, so it fails to compensate for the schema's weak text.

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 names a specific, well-defined computation: 'CAPM cost of equity and after-tax cost of debt combined into WACC,' which is unambiguous and clearly distinct from sibling valuation tools like dcf-valuation or peer-multiples. It stops short of explicitly naming an alternative, but the resource and method are concrete enough for an agent to route correctly.

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 context is implied by the input list ('from supplied equity and debt values'), signaling this is a computation over caller-provided inputs rather than a data-fetch tool. There is no explicit when-to-use versus when-not guidance, and no statement of prerequisites such as currency or unit consistency across the eight numeric inputs.

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