Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_crypto_mining_profitability

Calculate Bitcoin ASIC mining profitability from hash rate, power draw, electricity rate, BTC price, and network hashrate to estimate daily net profit and break-even power cost.

Instructions

Proof-of-Work Bitcoin Mining Profitability & Hash Rate Calculator. Calculate daily net profit, break-even electricity rate, and hardware payback for ASIC Bitcoin miners accounting for network difficulty and halving epochs. Discipline: CRYPTO. Governing mathematical model / formula: Daily BTC = (Hashrate in TH/s / Network Hashrate) × (Block Reward × 144 blocks/day) | Profit = Revenue - (kW × 24 × $/kWh).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of daily_net_profit (Daily Net Profit (After Power)), monthly_net_profit (Estimated Monthly Profit), daily_power_cost (Daily Electricity Expense), breakeven_power_cost (Shutdown Breakeven Power Cost) using asic_hashrate_ths (ASIC Miner Hashrate (TH/s) in TH/s), power_consumption_w (Miner Power Consumption (Watts) in Watts), electricity_cost_kwh (Electricity Rate ($/kWh)), bitcoin_price_usd (Bitcoin Market Price ($)), network_hashrate_ehs (Total Network Hashrate (EH/s) in EH/s). 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 'Proof-of-Work Bitcoin Mining Profitability & Hash Rate 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): "crypto-mining-profitability"

    • category (string): "crypto"

    • name (string): "Proof-of-Work Bitcoin Mining Profitability & Hash Rate Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.daily_net_profit (Daily Net Profit (After Power)): Formatted display string (e.g. '$4.55 / day')

      • metrics.monthly_net_profit (Estimated Monthly Profit): Formatted display string (e.g. '$136.50 / mo')

      • metrics.daily_power_cost (Daily Electricity Expense): Formatted display string (e.g. '$4.70 / day')

      • metrics.breakeven_power_cost (Shutdown Breakeven Power Cost): Formatted display string (e.g. '$0.128 / kWh')

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

Input Schema

NameRequiredDescriptionDefault
asic_hashrate_thsNoASIC Miner Hashrate (TH/s) (TH/s). Nominal hash rate (e.g. Antminer S19 XP = 140 TH/s). Default: 140. Min: 10. Max: 1000.
bitcoin_price_usdNoBitcoin Market Price ($). Current BTC spot price. Default: 65000. Min: 10000. Max: 500000.
power_consumption_wNoMiner Power Consumption (Watts) (Watts). Wall plug electricity consumption. Default: 3010. Min: 500. Max: 10000.
electricity_cost_kwhNoElectricity Rate ($/kWh). All-in hosting or utility power rate. Default: 0.065. Min: 0.01. Max: 0.3.
network_hashrate_ehsNoTotal Network Hashrate (EH/s) (EH/s). Global Bitcoin network hash rate. Default: 650. Min: 100. Max: 2000.

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 disclosure burden and does so: it declares the tool read-only, idempotent, stateless, with zero side effects, and specifies that out-of-bounds inputs return a diagnostic error status rather than throwing. It also documents the response envelope (status, calculator, inputs echo, metrics, execution_time_ms), which is behavior an agent cannot infer from the input schema.

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 definition is front-loaded with the formula and usage routing before the detail, which is the right ordering. There is mild redundancy — the floating-point precision claim appears in both the usage section and BEHAVIOR & SAFETY, and the RETURNS block restates metric display formats at length — but the extra length is largely justified because no output schema exists.

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?

For a five-parameter deterministic calculator with no output schema and no annotations, the definition covers everything an agent needs: the formula, the input-to-output mapping, error semantics, statelessness, and a full description of the returned JSON including metric key names and example formats. No material gap remains.

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 description coverage is 100%, so the baseline would be 3; the description earns above that by mapping each input (asic_hashrate_ths, power_consumption_w, electricity_cost_kwh, bitcoin_price_usd, network_hashrate_ehs) to the specific output metrics it drives, which clarifies the TH/s vs EH/s unit relationship. It stops short of adding new semantics like typical operating ranges beyond what the schema's min/max already state.

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 verb and resource — 'Proof-of-Work Bitcoin Mining Profitability & Hash Rate Calculator' — and immediately states the governing formula, so the agent knows it computes daily net profit, break-even electricity rate, and hardware payback. It also distinguishes itself from generic dispatchers by name, so no schema inspection is needed to tell it apart.

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 section names the exact output metrics and inputs that trigger this tool, and WHEN NOT TO USE excludes qualitative/unquantified reasoning. SIBLING ROUTING names omni_universal_query as the generic alternative and points to it for cross-discipline dispatch, giving a concrete decision rule.

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