Skip to main content
Glama

Startup Valuation MCP Server

Probability & Expected Value

valuation_probability
Read-onlyIdempotent

Compute expected value and probability-weighted outcomes for startup scenarios: discrete E[X], joint probability of sequential events, probability-weighted value, VC portfolio expected return, Poisson event probability, and continuous E[X] over a range. Method selects the formula. Use for probability-weighted central estimates; for named bull/base/bear tables or option pricing use valuation_advanced, and to discount cash flows use valuation_time_value. Parameters apply per method: expected_value_discrete and probability_weighted need outcomes + probabilities; portfolio_return needs weights + returns; poisson needs mean_events + k; expected_value_continuous needs lower + upper. outcomes and probabilities must be equal length, and the probabilities should sum to 1. Routing: use valuation_advanced method 'scenario_analysis' for named bull/base/bear scenario tables, and its black_scholes/binomial methods for option pricing; use this tool for arbitrary outcome lists and probability-weighted central estimates. Only method is required; all other parameters are method-dependent, so supply those the selected method names and omit the rest (defaults apply where defined). Rate and decimal inputs are fractions (0.10 = 10%); probability and weight lists are in [0,1] and sum to 1. Returns value, method, inputs, assumptions, chapter, formula_number and calculation steps; pure arithmetic — no I/O and no external calls — rounded to 2 decimals, with no auth or rate limits. An unknown method, or a missing method-required parameter, returns an error instead of a value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoNumber of events k for the Poisson probability P(X=k).
lowerNoLower integration bound (standard-normal domain, e.g. -1.0).
upperNoUpper integration bound (standard-normal domain, e.g. 1.0).
methodYesFormula to apply. Options: expected_value_discrete = E[X] = Σ xᵢ·P(X=xᵢ) over a discrete outcome list.; joint_probability = P(total) = Π pᵢ for independent sequential events.; probability_weighted = E[V] = Σ pᵢ·Vᵢ.; portfolio_return = E[R] = Σ wᵢ·Rᵢ across a VC portfolio.; poisson = P(X=k) = e^-λ λ^k / k! for rare events.; expected_value_continuous = E[X] = ∫ x·f(x) dx over [lower, upper] on the standard normal.
returnsNoReturn of each asset or scenario as a decimal (0.20 = 20%), aligned with weights.
weightsNoPortfolio or factor weights, each in [0,1] and summing to 1 (same order as the paired value list).
outcomesNoPossible outcome values x_i, in any currency unit (must match probabilities in length/order).
mean_eventsNoPoisson mean λ = expected number of events in the interval.
probabilitiesNoProbability of each outcome or stage, each in [0,1]; the list must sum to 1 where it is exhaustive.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message when the call fails.
stepsNoIntermediate steps for traceability.
valueYesComputed valuation or metric.
inputsNoEcho of the normalised inputs used.
methodNoFormula / method name that produced the result.
chapterNoSource textbook chapter.
assumptionsNoModelling assumptions applied.
formula_numberNoSource textbook formula number (e.g. '3.1').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which already declare read-only, idempotent, closed-world, non-destructive), the description adds the crucial behavioral facts: pure arithmetic with no I/O or external calls, results rounded to 2 decimals, no auth or rate limits, and explicit failure behavior (unknown method or missing method-required parameter returns an error). This is substantive context the annotations cannot convey.

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 purpose, then method, then routing, then constraints — a sensible order. However, the routing guidance is stated twice (the 'Use for...' sentence and the later 'Routing:' sentence repeat the valuation_advanced guidance), which is redundant in an otherwise dense block.

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?

For a nine-parameter, six-method calculation tool with an output schema, the description covers method selection, per-method parameter requirements, unit conventions, error behavior, and return shape. Nothing an agent needs to invoke it correctly 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, but the description goes further by mapping each method to its required parameters (outcomes+probabilities, weights+returns, mean_events+k, lower+upper) and stating cross-field constraints (equal length lists, probabilities summing to 1, fractions vs. [0,1] domains). Only the pairing/ordering details remain purely in the schema.

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?

The description names the specific computation (expected value and probability-weighted outcomes) and enumerates the six supported formulas, giving a concrete verb+resource. It explicitly distinguishes itself from the sibling valuation_advanced (named bull/base/bear tables, option pricing) and valuation_time_value (discounting cash flows), so an agent can select it without opening other schemas.

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?

It states when to use this tool ('probability-weighted central estimates', 'arbitrary outcome lists') and when not to, naming the alternative tool and even the specific sibling methods (scenario_analysis, black_scholes/binomial) that should be used instead. The routing rules are explicit rather than inferred.

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.