Skip to main content
Glama

Stratalize Intelligence

Get Ma Multiples Benchmark

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior: the underlying provenance ('Damodaran transaction dataset and public deal aggregates') and a metered cost of '$0.02 USDC per call' that an agent must know before calling. It does not say how stale the data is, how tiers are aggregated, or what the payload looks like, so it is useful but incomplete.

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?

It is front-loaded with the usage trigger, then the data, then the source, then the audience, then price — a sensible order with no wasted clauses. It is slightly padded, though: 'preparing a fairness opinion' appears twice (trigger and audience), and the audience list ('corp dev, PE deal teams, M&A advisors, and CFOs') duplicates information the trigger already implied.

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 read-only, two-enum-parameter lookup with no output schema, the definition is nearly sufficient: source, coverage, cost, and triggers are all stated. What is missing is the behavior of the optional deal_size_tier when omitted (aggregate across tiers vs. error) and any indication of return shape or period coverage. Those gaps are small but material to calling it correctly.

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 burden. The phrase 'by industry and deal size' ties the two parameters to their analytical dimension and confirms they segment the multiple, which the bare enum schema does not convey. However, it does not explain what omitting the optional deal_size_tier does, nor what the enum buckets mean economically, leaving a real gap for a 0%-coverage schema.

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 resource and its contents: 'M&A transaction multiples — acquisition EV/EBITDA, EV/Revenue, and control premiums by industry and deal size.' That is far more than a restatement of the title and lets an agent distinguish it from a generic public-comps tool. It stops short of explicitly contrasting with the sibling get_public_market_multiples, which would have made it a 5.

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 opens with concrete triggers: 'Use when valuing an acquisition target, benchmarking deal pricing, or preparing a fairness opinion.' That is clear when-to-use guidance rather than an implied scope. It gives no when-not-to-use conditions and names no alternative for public-market (non-transaction) comps, so it falls short of explicit routing.

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