Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_yield_farming_reinvest_frequency

Calculate the optimal DeFi yield farming reinvestment frequency to balance compound APY against harvest gas fees, returning net APY, annual gas cost, and compounding boost.

Instructions

Optimal Compounding Frequency for DeFi Yield Farming Calculator. Calculate the mathematically optimal reinvestment frequency that maximizes compound APY while minimizing transaction gas harvesting fees. Discipline: CRYPTO. Governing mathematical model / formula: Optimal Days Between Harvests = √[(2 · Gas Cost in USD) / (Principal · Daily APR · Daily Yield)].

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of optimal_reinvest_interval (Optimal Compounding Interval), net_apy_after_gas (Net Effective APY (After Gas)), annual_harvest_gas_cost (Total Annual Gas Spend), compounding_boost_usd (Net Dollar Value Added by Compounding) using farming_principal_usd (Farmed Capital Value ($ USD)), nominal_farm_apr_pct (Nominal Stated Farm APR (%) in %), harvest_gas_cost_usd (Harvest & Re-stake Gas Fee ($)). 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.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Optimal Compounding Frequency for DeFi Yield Farming Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

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): "yield-farming-reinvest-frequency"

    • category (string): "crypto"

    • name (string): "Optimal Compounding Frequency for DeFi Yield Farming Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.optimal_reinvest_interval (Optimal Compounding Interval): Formatted display string (e.g. 'Every 4.8 Days')

      • metrics.net_apy_after_gas (Net Effective APY (After Gas)): Formatted display string (e.g. '53.8% APY')

      • metrics.annual_harvest_gas_cost (Total Annual Gas Spend): Formatted display string (e.g. '$494.00 / yr')

      • metrics.compounding_boost_usd (Net Dollar Value Added by Compounding): Formatted display string (e.g. '+$1,320.00 / yr')

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

Input Schema

NameRequiredDescriptionDefault
harvest_gas_cost_usdNoHarvest & Re-stake Gas Fee ($). All-in transaction cost to claim, swap, and restake. Default: 6.5. Min: 0.01. Max: 100.
nominal_farm_apr_pctNoNominal Stated Farm APR (%) (%). Uncompounded reward token emission APR. Default: 45. Min: 5. Max: 500.
farming_principal_usdNoFarmed Capital Value ($ USD). Principal deposited in liquidity farm. Default: 15000. Min: 250. Max: 1000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does so well: read-only, idempotent, stateless, zero side effects, bounded input validation that returns a diagnostic error instead of throwing. It stops short of stating tolerance/precision limits or behavior at extreme-but-valid bounds, so it is strong but not exhaustive.

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?

Sectioned and front-loaded, with the purpose and formula before the operational detail. Some redundancy exists (the formula is restated in the RETURNS block) and the RETURNS tree is long, but it stays scannable and each block maps to a decision the agent must make.

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 and no annotations exist, yet the description fully specifies the response envelope, every metric key with example formatting, and the safety/validation posture. An agent can call this tool and interpret the result without any other source.

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 the default baseline is 3; the description adds value by tying each named input (farming_principal_usd, nominal_farm_apr_pct, harvest_gas_cost_usd) to the outputs it drives via the stated formula. It restates units and role but does not add new constraints 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 resource (optimal compounding frequency for DeFi yield farming), gives the exact governing formula, and enumerates the four metrics produced. It is immediately distinguishable from generic siblings like omni_universal_query and from adjacent yield tools such as omni_liquidity_pool_fee_yield.

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 and WHEN NOT TO USE sections state the deterministic-calculation use case and exclude qualitative reasoning, plus a DISAMBIGUATION block routing multi-step jobs to omni_batch_calculate and schema inspection to omni_describe_solver. The only minor gap is that omni_algorithmic_lending_apy is not mentioned as an adjacent alternative, but the named routing is sufficient.

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