Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_fire

Calculate your FIRE number, lean FIRE target, and years to financial independence from expenses, savings, net worth, and withdrawal rate.

Instructions

FIRE Calculator (Financial Independence, Retire Early). Calculate your exact FIRE Number, Lean/Fat FIRE targets, and time to complete financial freedom using Trinity Study safe withdrawal rates. Discipline: FINANCE. Governing mathematical model / formula: FIRE Number = Annual Living Expenses / Safe Withdrawal Rate (e.g. Expenses × 25).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of fire_number (Target FIRE Nest Egg), years_to_fire (Timeline to Financial Freedom), lean_fire (Lean FIRE (75% Expenses)) using annual_expenses (Annual Living Expenses), current_net_worth (Current Invested Net Worth), annual_savings (Annual Savings Contribution), swr_pct (Safe Withdrawal Rate (%) in %), real_return (Inflation-Adjusted Real Return (%) in %). 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 'FIRE Calculator (Financial Independence, Retire Early)' 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): "fire"

    • category (string): "finance"

    • name (string): "FIRE Calculator (Financial Independence, Retire Early)"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.fire_number (Target FIRE Nest Egg): Formatted display string (e.g. '$1,500,000.00')

      • metrics.years_to_fire (Timeline to Financial Freedom): Formatted display string (e.g. '14.2 years')

      • metrics.lean_fire (Lean FIRE (75% Expenses)): Formatted display string (e.g. '$1,125,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_fire"
  }
}

Input Schema

NameRequiredDescriptionDefault
swr_pctNoSafe Withdrawal Rate (%) (%). 4% standard (Trinity study); 3.25%-3.5% for early retirees. Default: 4. Min: 3. Max: 5.
real_returnNoInflation-Adjusted Real Return (%) (%). Real return after subtracting inflation. Default: 6.5. Min: 3. Max: 10.
annual_savingsNoAnnual Savings Contribution. Total saved and invested per year. Default: 35000. Min: 0. Max: 300000.
annual_expensesNoAnnual Living Expenses. Target retirement spending per year. Default: 60000. Min: 10000. Max: 500000.
current_net_worthNoCurrent Invested Net Worth. Current liquid investable assets. Default: 180000. Min: 0. Max: 5000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/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 well: it declares pure deterministic computation, read-only/idempotent/stateless behavior, zero side effects, input validation against domain bounds, and safe diagnostic error returns without runtime exceptions. It also explains the structured success/error response shape.

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 front-loaded with the calculator purpose and formula, then organized into USAGE GUIDELINES, BEHAVIOR & SAFETY, and RETURNS. It is longer than necessary because the return object is described in heavy detail, but the structure keeps it navigable and every major section has a clear role.

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?

Although there is no output schema, the description fully documents the JSON return shape including status, calculator, category, name, formula, inputs, metrics, and execution_time_ms. For a parameterized deterministic calculator with validation behavior, this is complete enough for an agent to call and interpret results correctly.

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%, so the schema already documents each parameter's meaning, defaults, min, and max. The description lists the parameter names and adds the governing formula context, but does not add much semantic detail beyond the schema's own parameter documentation.

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 states a specific verb/resource: a FIRE calculator computing fire_number, years_to_fire, and lean_fire using the FIRE Number formula. It also distinguishes itself from generic dispatchers like omni_universal_query, so an agent can identify its role 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 an explicit WHEN TO USE section listing the deterministic calculations and parameters, a WHEN NOT TO USE section excluding qualitative reasoning, and SIBLING ROUTING that names omni_universal_query as the alternative for dynamic dispatch. This is unusually complete routing guidance.

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