Skip to main content
Glama

get_ma_multiples_benchmark

Read-only

Use when valuing an acquisition target, benchmarking deal pricing, or preparing a fairness opinion. M&A transaction multiples — acquisition EV/EBITDA, EV/Revenue, and control premiums by industry and deal size. Source: Damodaran transaction dataset and public deal aggregates. Used by corp dev, PE deal teams, M&A advisors, and CFOs preparing fairness opinions. $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": {
      "industry": "<industry>"
    },
    "name": "get_ma_multiples_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryYes
deal_size_tierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new context: the data provenance (Damodaran transaction dataset plus public deal aggregates) and a per-call cost of $0.02 USDC, which matters for an agent deciding whether to invoke. It does not describe the response shape, but that is a minor gap given the metric list.

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?

Front-loads the use case, then the resource, then provenance, audience, and price in short declarative sentences. Slightly list-like with the audience enumeration, but every sentence carries information and nothing is redundant.

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?

With no output schema, the description compensates by naming the returned metrics (EV/EBITDA, EV/Revenue, control premiums) and the data source. For a two-parameter read-only lookup this is close to complete; only the deal-size tier definitions are left unexplained.

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 parameter meaning. It only says results are broken out 'by industry and deal size', which loosely maps to the two parameters, but it never explains the deal_size_tier boundaries (under_50m, 50m_250m, etc.) or what the industry enum values imply. The enums are largely self-describing, keeping this at a minimum-viable 3.

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 resource — M&A transaction multiples (acquisition EV/EBITDA, EV/Revenue, control premiums) — with scope qualifiers 'by industry and deal size'. The 'M&A transaction' framing implicitly separates it from the public-market multiples sibling, though no sibling is named explicitly.

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?

Gives three concrete triggering scenarios: valuing an acquisition target, benchmarking deal pricing, and preparing a fairness opinion. It does not state when to prefer an alternative (e.g., public-market multiples) or any exclusions, 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