Skip to main content
Glama

Business valuation calculator

Business valuation estimate

value_business
Read-onlyIdempotent

Estimates what a buyer might pay for a small agency, productized service, consultancy or software (SaaS) business. Returns a worst case, a base case and a best case in US dollars, from published US sale prices. An estimate, not a formal valuation.

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": {
      "type": "<type>",
      "revenue": "<revenue>",
      "profit": "<profit>"
    },
    "name": "value_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesThe kind of business. A productized service sells a fixed scope for a fixed price.
churnNoSoftware only. Customers lost each month: low (under 2%), mid (2% to 5%), high (over 5%).
growthNoRevenue in the last 12 months: down (it dropped), flat (flat or up less than 10%), up (up 10% to 30%), fast (up more than 30%).
profitYesProfit before tax for the last 12 months, after the owner's pay. A loss is a negative number.
revenueYesRevenue for the last 12 months, in US dollars.
owner_payNoWhat the owner took in salary, bonuses and personal costs in the same 12 months. 0 when not given.
recurringNoService businesses only. Share of revenue on retainer, subscription or contract: low (under 30%), mid (30% to 60%), high (over 60%).
top_clientNoShare of revenue from the biggest client: low (under 15%), mid (15% to 25%), high (over 25%).
founder_dependenceNoHow much the business needs its founder for sales, client contact and decisions: low (it runs without the founder), mid, high (it needs the founder for everything).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior: the estimate derives from published US sale prices and always returns a worst/base/best-case triplet in USD, which is not derivable from annotations or schema.

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?

Three short sentences, front-loaded with purpose, then return shape, then the caveat. Every sentence earns its place with no repetition of the title or schema.

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 correctly explains the return value (worst/base/best case in USD) and the pricing basis, which is what an agent most needs. It stops short of noting how optional inputs affect confidence or any input-range limits, but the required/optional split is already in the schema.

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 100%, including enum semantics and conditional applicability (churn for software, recurring for service businesses), so the schema does the heavy lifting. The description adds no per-parameter meaning beyond that baseline.

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 ("Estimates") and a precise resource (what a buyer might pay for a small agency, productized service, consultancy or SaaS business). The supported business types match the schema enum exactly, so an agent knows the scope without opening the input 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?

The closing line "An estimate, not a formal valuation" sets a clear expectation boundary about when the output is and isn't appropriate. It doesn't name alternative tools (none exist among siblings), so there is nothing further to route against.

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