Skip to main content
Glama

get_wacc_benchmark

Read-only

Use when valuing a business, setting hurdle rates, or benchmarking discount rates for M&A analysis or capital allocation. WACC benchmarks by sector and market cap tier from Damodaran annual dataset — used for DCF valuation, M&A pricing, board approval, and capital allocation. The most cited public finance benchmark. Updated January annually. $0.02 USDC per call.

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": {
      "sector": "<sector>"
    },
    "name": "get_wacc_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYes
market_cap_tierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false). The description adds genuinely useful context that annotations cannot: provenance (Damodaran), refresh cadence (updated January annually), and cost ($0.02 USDC per call), which matters for an agent deciding whether to spend. It says nothing about latency or the shape of the returned figures.

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?

Usage trigger is front-loaded, followed by what it returns, provenance, cadence, and price. It loses a small amount to redundancy: 'M&A analysis or capital allocation' in sentence one is repeated as 'M&A pricing, board approval, and capital allocation' in sentence two.

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 simple two-parameter lookup with no output schema, the description should at least indicate what comes back — a single rate, or a component breakdown such as cost of equity, cost of debt, beta, and tax rate. It establishes the source and freshness but leaves the return content underspecified.

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 burden falls on the description, which only restates that results are 'by sector and market cap tier'. The enum values are largely self-explanatory, but the description never explains what the tiers mean in size terms, nor what happens when the optional market_cap_tier is omitted.

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 names a specific metric (WACC benchmarks) plus the two dimensions it is keyed on (sector, market cap tier) and its source (Damodaran annual dataset). This clearly separates it from siblings such as get_cap_rate_benchmark or get_credit_spread_benchmark without needing to open any schema.

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

Usage Guidelines4/5

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

It gives concrete when-to-use contexts: valuing a business, setting hurdle rates, DCF valuation, M&A pricing, board approval, capital allocation. It does not name a specific alternative tool or state when not to use it, so it stops short of full routing guidance.

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