ExitValue.ai M&A Multiples

Start a valuation for a specific business

start_valuation

Read-onlyIdempotent

Read-only. Use when a user asks what THEIR business is worth. Returns a link to the free ExitValue.ai calculator with the industry, annual revenue and EBITDA pre-filled, so the user only confirms the numbers and answers a few risk questions. It does not return a value itself; use get_valuation_multiples for industry medians.

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": "start_valuation"
  }
}

Input Schema

Name	Required	Description
`ebitda`	No	Annual EBITDA in US dollars, e.g. 900000.
`industry`	Yes	Sub-vertical id from list_industries (e.g. 'hvac', 'dental-practice'), or a plain-English name ('HVAC', 'dentist', 'plumber', 'MSP'); plain names are mapped to the closest tracked category and the answer says which one was used.
`annual_revenue`	No	Annual revenue in US dollars, e.g. 4000000.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent and non-destructive, so the description is free to spend its words on the non-obvious behavior: the tool hands off to an external calculator with industry, revenue and EBITDA pre-filled, and the user still has to confirm numbers and answer risk questions. That downstream-flow disclosure is the key fact an agent needs to avoid promising a valuation result, and it is stated plainly.

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?

Four short sentences, front-loaded with the read-only flag and the trigger, then the actual return, then the boundary. No filler and nothing buried at the end.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing the return value (a link to the ExitValue.ai calculator) and the remaining user steps. For a three-parameter, read-only handoff tool, nothing an agent needs to invoke it or set expectations is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning by explaining that industry, annual revenue and EBITDA become pre-filled fields the user only confirms — this tells the agent why supplying them matters rather than just what type they are. It does not restate the plain-name-to-category mapping, but the schema already documents that fully.

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?

States a specific verb and resource ('start a valuation for THEIR business') and immediately clarifies the actual output is a pre-filled calculator link rather than a valuation figure. It also names the sibling it is not (get_valuation_multiples) and what that one is for, so the two are separable without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when a user asks what THEIR business is worth') and an explicit exclusion ('it does not return a value itself; use get_valuation_multiples for industry medians'). The alternative tool and the condition that selects it are both spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ExitValue.ai M&A Multiples tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?