Skip to main content
Glama

Weighted Average Cost of Capital

bpj_weighted_capital_cost
Read-onlyIdempotent

Weight the after-tax cost of debt and cost of equity by their market values to calculate WACC.

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": {
      "debt": "<debt>",
      "equity": "<equity>",
      "costDebt": "<costDebt>",
      "costEquity": "<costEquity>",
      "tax": "<tax>"
    },
    "name": "bpj_weighted_capital_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxYes
debtYes
equityYes
costDebtYes
costEquityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral substance by disclosing the computation itself — debt cost is applied after tax, and both components are weighted by market values — but it says nothing about the result's form (percentage vs. decimal), rounding, or error behavior for degenerate inputs like debt = equity = 0.

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?

A single sentence with no filler, and the core operation is front-loaded. It is dense but well-formed; nothing needs to be trimmed.

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

Completeness3/5

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

For a five-required-parameter calculator with no output schema and no parameter descriptions, the definition should confirm the output form and how the weights are derived. It conveys the essential mechanics but stops short of the detail needed to call it confidently without guessing at units and result format.

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 0%, so the description must carry the load, and it does partially: 'after-tax cost of debt' tells the agent that tax applies to costDebt and not costEquity, and 'by their market values' identifies debt and equity as the weighting basis. However, it never states the units or the exact weighting formula (debt/(debt+equity)), leaving the agent to infer how the five required numbers combine.

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?

States a specific verb ('weight ... to calculate') and a named, unambiguous output (WACC), plus the inputs being weighted. The agent can tell this is a capital-cost calculator rather than a generic averaging tool, though it does not explicitly differentiate itself from siblings like bpj_return_on_invested_capital or the various 'cost' tools.

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?

There is no when-to-use guidance, no prerequisites stated, and no naming of an alternative tool or condition that would select one. The usage context (valuation / capital budgeting) is only implied by the WACC acronym.

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.