Startup Valuation MCP Server

Marketplace Metrics

valuation_marketplace

Read-onlyIdempotent

Marketplace health and valuation: take rate, GMV revenue-multiple valuation, buyer retention, and network density. Method selects the metric. Use for two-sided transaction marketplaces; for subscription software use valuation_saas. Parameters apply per method: take_rate needs revenue + gmv; gmv_multiple needs gmv + multiple; buyer_retention needs buyers_period_1 + buyers_repeat; network_density needs active_buyers + active_sellers + total_users. 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

Name	Required	Description
`gmv`	No	Gross merchandise value (total transaction volume), currency units.
`method`	Yes	Formula to apply. Options: take_rate = Take rate = revenue / GMV.; gmv_multiple = Valuation = GMV × multiple.; buyer_retention = Retention = repeat buyers / base-period buyers.; network_density = Density = active buyers × active sellers / total users.
`revenue`	No	Revenue for the period, currency units.
`multiple`	No	Exit or market multiple applied to the metric.
`total_users`	No	Total users (buyers + sellers) in the period.
`active_buyers`	No	Active buyers in the period.
`buyers_repeat`	No	Distinct buyers from the base period who purchased again.
`active_sellers`	No	Active sellers in the period.
`buyers_period_1`	No	Distinct buyers in the base period.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Error message when the call fails.
`steps`	No	Intermediate steps for traceability.
`value`	Yes	Computed valuation or metric.
`inputs`	No	Echo of the normalised inputs used.
`method`	No	Formula / method name that produced the result.
`chapter`	No	Source textbook chapter.
`assumptions`	No	Modelling assumptions applied.
`formula_number`	No	Source textbook formula number (e.g. '3.1').
`defaults_applied`	No	Optional parameters that were not supplied, so their documented defaults were used.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations cover read-only/idempotent/no-side-effects, and the description adds rich context beyond them: it discloses the retrieval/return payload (value, method, inputs, assumptions, chapter, formula_number, calculation steps), rounding to 2 decimals, no I/O, no auth, no rate limits, and explicit error behavior for unknown method or missing required params.

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?

Front-loaded with purpose, then method-to-parameter mapping, then behavioral notes. Dense but every sentence carries information; only reason for docking is that the parameter-method mapping sentence is a long run-on that could be split.

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?

Coverage is comprehensive: purpose, method selection, per-method params, input conventions (fractions, [0,1] weights), required-only-method rule, default behavior, and error semantics are all present. Output schema exists, so return-value explanation is supplementary rather than required.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3, but the description adds semantic constraints not present in the schema: rate/decimal inputs are fractions, probability/weight lists are in [0,1] and sum to 1, only method is required, and the mapping of which params each method needs vs. when defaults apply.

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?

Description states a specific verb+resource ('Marketplace health and valuation') and enumerates the four metrics computed (take rate, GMV multiple, buyer retention, network density). It explicitly distinguishes itself from the sibling valuation_saas ('for subscription software use valuation_saas').

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?

Provides a clean routing rule: use for two-sided transaction marketplaces; use valuation_saas for subscription software. Also explains that method selects the metric and which parameters each method requires.

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

All Startup Valuation MCP Server 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.