Skip to main content
Glama

tvm-fund

calculate_tvpi

Read-onlyIdempotent

Calculate Total Value to Paid-In capital (TVPI): (distributions + residual value) divided by paid-in capital — the total multiple of a fund or investment including both realised and unrealised value. Formula: TVPI = (Distributions + Residual Value) / Paid-In Capital. WHEN TO USE: Use as the headline multiple for private equity / venture fund performance (equivalent to DPI + RVPI). WHEN NOT TO USE: Do NOT use TVPI to compare funds of different vintages/ages — it ignores the time value of money (use IRR or MOIC-with-hold-period for time-adjusted comparison). BEHAVIOUR: pure deterministic calculation — no side effects, no network or storage access; idempotent and non-destructive; identical inputs always produce identical outputs. Division by zero, non-finite inputs, or mathematically undefined combinations return an explicit error instead of a number. RETURNS: JSON object { tvpi: number (e.g. 2.0 = 2.0x total value on paid-in), inputs }. PARAMETERS: distributions (required): Cumulative distributions returned to investors, e.g. 800000. Must be >= 0. residual_value (required): Current fair value of remaining investments, e.g. 1200000. Must be >= 0. paid_in (required): Paid-in capital, e.g. 1000000. Must be > 0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paid_inYesPaid-in capital, e.g. 1000000. Must be > 0.
distributionsYesCumulative distributions returned to investors, e.g. 800000. Must be >= 0.
residual_valueYesCurrent fair value of remaining investments, e.g. 1200000. Must be >= 0.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive hints, but the description adds valuable behavioral detail: no side effects, no network/storage access, deterministic output, and explicit error handling for division by zero or non-finite inputs. This goes well beyond the structured annotations and defines expected edge-case behavior.

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?

The description is well-structured with clear caps-locked sections and is easy to scan. However, the formula is effectively stated twice: once in the opening sentence and again in the explicit 'Formula:' line, which is mild redundancy. Overall, every major section earns its place.

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?

The description is fully self-contained: it defines the formula, explains when to use and avoid the metric, describes behavior and error handling, specifies the return JSON shape, and documents all three required parameters. Since there is no output schema, the explicit RETURNS section fills that gap completely.

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%, and the parameter descriptions in the schema already include examples and constraints. The description repeats these details and adds formula context, but it does not provide substantial new parameter-level meaning beyond what the schema already documents.

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 a specific calculation (TVPI), states the exact formula, and clarifies what the result means ('total multiple of a fund or investment including both realised and unrealised value'). It also connects to sibling tools by noting it is equivalent to DPI + RVPI, making it easy to distinguish from the other calculate_* tools.

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?

The WHEN TO USE section specifies the intended context (headline multiple for PE/VC fund performance), and the WHEN NOT TO USE section explicitly warns against comparing different vintages and recommends alternatives (IRR or MOIC-with-hold-period). This gives an agent clear decision criteria.

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.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a mathematically distinct calculation (single-sum PV/FV, annuity, perpetuity, payback, fund multiples). The descriptions include explicit 'WHEN TO USE' and 'WHEN NOT TO USE' sections with cross-references, making it unambiguous which tool applies to which scenario.

Naming Consistency5/5

All tool names follow the exact pattern verb_noun with the consistent 'calculate_' prefix (e.g., calculate_present_value, calculate_payback_period). The naming convention is uniform across the entire set.

Tool Count5/5

11 tools is well within the ideal range for a focused domain. Each tool addresses a distinct calculation relevant to time-value-of-money and fund performance, with no redundant entries.

Completeness3/5

The set covers many core calculations but is missing NPV and IRR, which are explicitly referenced as the recommended tools in several descriptions (e.g., payback periods, TVPI). This creates a notable gap that could lead agents to follow cross-references to non-existent tools.

Resources