Skip to main content
Glama
Sign In
mcp-server-valuation

mcp-server-valuation

by tudadada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

calc_ebitda_multiple

Calculate target acquisition value from annual revenue or EBITDA using industry-standard multiples for saas, ecommerce, agency, or content.

Instructions

Calculates target acquisition value based on annual revenue/EBITDA and industry-standard multiples.

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": {
      "annual_revenue_usd": "<annual_revenue_usd>",
      "ebitda_usd": "<ebitda_usd>"
    },
    "name": "calc_ebitda_multiple"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryNoIndustry vertical: saas, ecommerce, agency, content
ebitda_usdYesEarnings before interest, taxes, depreciation in USD
annual_revenue_usdYesAnnual recurring revenue in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it discloses little: 'industry-standard multiples' is vague about which multiples or formula are applied, and it never says whether the result is a single number, a range, or whether the call has any side effects. It does at least convey the calculation method's basis, which is some behavioral context.

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 front-loaded sentence with no filler, though it is arguably too terse given the gaps in usage and behavior disclosure.

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 three-parameter pure calculation with no annotations and no output schema, the description covers the basic mechanics but omits what the return value looks like and how industry affects the result. Adequate but with clear gaps.

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 coverage is 100%, so all three parameters, including the industry enum-like values, are already documented in the schema. The description adds only the idea that industry drives the multiple, which is a marginal restatement of the schema. Baseline 3 applies.

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 verb (Calculates) and a specific resource (target acquisition value), plus the inputs that drive it (annual revenue/EBITDA, industry multiples). It is clear what the tool produces, though it never references or distinguishes itself from the sibling value_digital_asset.

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 statement of when to use this tool versus value_digital_asset, nor any prerequisites or exclusions. Usage can only be inferred from the phrase 'target acquisition value,' which is not enough to route between two valuation tools.

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

Deploy Server

Other Tools