Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_viral_coefficient

Calculates viral coefficient (K-factor), growth multiplier, and new users from invites sent, conversion rate, and cohort size to quantify referral-driven expansion and classify virality.

Instructions

Viral Coefficient (K-Factor) & Growth Calculator. Calculate K-factor viral expansion, viral cycle time, customer compounding multiplier, and organic user generation. Discipline: FINANCE. Governing mathematical model / formula: K = Number of Invites per User × Referral Conversion Rate %.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of k_factor_score (Viral Coefficient (K-Factor)), virality_status (Virality Classification), viral_multiplier (Total Growth Multiplier), cycle1_growth (Cycle 1 New Viral Users) using invites_sent (Invites Sent per Customer in invites), conversion_rate_pct (Invite Acceptance / Conversion Rate in %), initial_cohort (Initial Cohort Size). 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 'Viral Coefficient (K-Factor) & Growth 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): "viral-coefficient"

    • category (string): "finance"

    • name (string): "Viral Coefficient (K-Factor) & Growth Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.k_factor_score (Viral Coefficient (K-Factor)): Formatted display string (e.g. '1.13')

      • metrics.virality_status (Virality Classification): Formatted display string (e.g. 'True Exponential Virality (K > 1.0)')

      • metrics.viral_multiplier (Total Growth Multiplier): Formatted display string (e.g. 'Infinite (Self-Sustaining Exponential)')

      • metrics.cycle1_growth (Cycle 1 New Viral Users): Formatted display string (e.g. '1,125 users')

    • 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_viral_coefficient"
  }
}

Input Schema

NameRequiredDescriptionDefault
invites_sentNoInvites Sent per Customer (invites). Average referral invitations sent by each user. Default: 4.5. Min: 0.1. Max: 50.
initial_cohortNoInitial Cohort Size. Starting seed user population. Default: 1000. Min: 10. Max: 1000000.
conversion_rate_pctNoInvite Acceptance / Conversion Rate (%). Percentage of invited users who register. Default: 25. Min: 1. Max: 100.

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 burden and meets it: pure deterministic computation with machine floating-point precision, read-only/idempotent/stateless with zero side effects, and explicit out-of-bounds behavior (safe diagnostic error status rather than a thrown exception). This discloses failure modes, not just success paths.

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 the calculator name and formula, then cleanly sectioned into USAGE, BEHAVIOR, and RETURNS. It is somewhat verbose: the long bracketed label 'Viral Coefficient (K-Factor) & Growth Calculator' and its metric aliases are repeated many times, and the RETURNS examples could be trimmed.

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?

No output schema exists, and the description fully compensates with a structured RETURNS block enumerating status, calculator, category, name, formula, echoed inputs, the four computed metrics, and execution_time_ms. Error semantics and validation bounds are also covered, so an agent has everything needed to call and interpret the result.

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 bounds and defaults are already documented; the description adds meaning by tying each parameter to its role in the formula (invites_sent as invites per customer, conversion_rate_pct as invite acceptance rate, initial_cohort as seed population) and to the specific output metric it drives. The unit re-statement ('in invites', 'in %') partially duplicates the schema, keeping it below a 5.

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 and resource ('Calculate K-factor viral expansion, viral cycle time, customer compounding multiplier, and organic user generation') and names the exact governing formula K = Invites per User × Referral Conversion Rate %. An agent can tell immediately this is a finance-domain deterministic calculator, not a query tool.

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?

Explicit WHEN TO USE (deterministic computation of k_factor_score, virality_status, viral_multiplier, cycle1_growth from named inputs), WHEN NOT TO USE (qualitative evaluation, non-numerical inputs), and SIBLING ROUTING ('rather than generic dispatchers like omni_universal_query'). All routing conditions are stated, not inferred.

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