Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_preferred_return_waterfall

Calculate private equity syndication waterfall distributions, splitting LP preferred returns and GP promote payouts at defined hurdles.

Instructions

Syndication Preferred Return & Waterfall Equity Calculator. Calculate private equity syndication waterfall distributions between General Partners (GP) and Limited Partners (LP) with preferred returns and promote hurdles. Discipline: FINANCE. Governing mathematical model / formula: Hurdle 1: 100% to LP until 8% Pref | Hurdle 2: 80% LP / 20% GP Promote Split.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of lp_total_payout (Limited Partner (LP) Total Distribution), gp_promote_payout (General Partner (GP) Promote Distribution), lp_pref_hurdle_dollar (LP 8.0% Preferred Return Amount), excess_split_cash (Distributable Cash Above Hurdle) using lp_capital_invested (Limited Partner (LP) Capital Invested), lp_preferred_return_pct (LP Preferred Return (Pref Rate %) in %), gp_promote_split_pct (GP Promote Share Above Hurdle in %), total_distributable_cash (Total Cash Available for Distribution). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Syndication Preferred Return & Waterfall Equity Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "preferred-return-waterfall"

    • category (string): "finance"

    • name (string): "Syndication Preferred Return & Waterfall Equity Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.lp_total_payout (Limited Partner (LP) Total Distribution): Formatted display string (e.g. '$392,000.00 (87.1%)')

      • metrics.gp_promote_payout (General Partner (GP) Promote Distribution): Formatted display string (e.g. '$58,000.00 (12.9%)')

      • metrics.lp_pref_hurdle_dollar (LP 8.0% Preferred Return Amount): Formatted display string (e.g. '$160,000.00')

      • metrics.excess_split_cash (Distributable Cash Above Hurdle): Formatted display string (e.g. '$290,000.00')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_preferred_return_waterfall"
  }
}

Input Schema

NameRequiredDescriptionDefault
lp_capital_investedNoLimited Partner (LP) Capital Invested. Total equity contributed by outside passive investors. Default: 2000000. Min: 50000. Max: 100000000.
gp_promote_split_pctNoGP Promote Share Above Hurdle (%). Carried interest share to sponsor (e.g. 80/20 split = 20% GP). Default: 20. Min: 5. Max: 50.
lp_preferred_return_pctNoLP Preferred Return (Pref Rate %) (%). Annual hurdle return before GP receives promote. Default: 8. Min: 4. Max: 15.
total_distributable_cashNoTotal Cash Available for Distribution. Operating cash or refinancing/sale proceeds. Default: 450000. Min: 10000. Max: 20000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: read-only, idempotent, stateless, zero side effects, bounded input validation returning a diagnostic error status rather than throwing. This exceeds what a mutation/read annotation pair would have conveyed.

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 title, then WHEN TO USE / WHEN NOT TO USE / SIBLING ROUTING / BEHAVIOR / RETURNS sections make it highly scannable. It is, however, verbose: the 'eliminating LLM arithmetic mistakes and formula hallucinations' claim repeats the precision point, and the parenthetical label expansions add bulk.

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?

There is no output schema, yet the description enumerates the full return envelope (status, calculator, category, name, formula, inputs echo, metrics with examples, execution_time_ms). For a four-parameter pure-compute tool, nothing an agent needs to invoke or interpret it 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% with defaults and min/max already documented, so the baseline is 3. The description goes further by tying each parameter to its role in the hurdle model (pref rate consumed until the 8% hurdle, promote split applied only to excess cash), which the schema alone does not explain.

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 opens with a specific resource and verb: 'Syndication Preferred Return & Waterfall Equity Calculator' calculating LP/GP waterfall distributions with preferred returns and promote hurdles. It names the exact outputs (lp_total_payout, gp_promote_payout) and the governing model, so an agent can distinguish it from a generic dispatcher without opening the schema.

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 has explicit WHEN TO USE (deterministic computation of the four named metrics), WHEN NOT TO USE (qualitative reasoning, non-numeric inputs), and SIBLING ROUTING pointing to omni_universal_query for dynamic dispatch. The alternative is named with the condition that selects it.

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