MinerYield

Calculate profitability

calculate_profitability

Read-only

POST /api/v1/calculator — one-machine home/small-business profitability with the same solar/battery/grid leftover-watt model as the site. Required: hashrate, power, algorithm, elecCost. Optional: solarW, batteryCapacity, zipCode, powerSources. Example: 3 kW miner on solar by day, grid at $0.15/kWh at night → power=3000, elecCost=0.15, solarW=, powerSources={solar:true, battery:false, grid:true} (add batteryCapacity and battery:true to store leftover sun). Returns dailyProfit, dailyCost, solarSavings, runtimeHours, effectiveElecCost. Figures are MinerYield model estimates from live market inputs: estimates only, not investment, financial, or tax advice, and not ROI guarantees. Results vary with network difficulty, coin price, power cost, and hardware performance. Do your own research.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hashrate": "<hashrate>",
      "power": "<power>",
      "algorithm": "<algorithm>",
      "elecCost": "<elecCost>"
    },
    "name": "calculate_profitability"
  }
}

Input Schema

Name	Required	Description
`power`	Yes	Miner wall power in Watts (3000 = 3 kW). Used with solar/battery/grid to compute leftover watts and runtime.
`solarW`	No	Home/small-business solar array capacity in Watts (10000 = 10 kW). Used with Peak Sun Hours from zipCode. Solar generation is treated as free during the sun window; leftover watts can charge the battery.
`zipCode`	No	5-digit US ZIP for Peak Sun Hours. Defaults to the API-key owner profile, then 06716. Needed for a realistic solar-by-day estimate.
`elecCost`	Yes	Grid electricity price in USD per kWh (0.15 = 15 cents). Applied only to leftover watts after solar and battery. There is no separate day/night rate: solar covers the sun window, grid covers the rest at this price.
`hashrate`	Yes	Hashing power (TH/s for SHA-256, MH/s for Scrypt; same units as the catalog).
`algorithm`	Yes	Catalog algorithm name as stored on MinerYield (SHA-256, Scrypt, KHeavyHash, Eaglesong, SHA512256d, Blake2B, Blake2B-Sia, Blake2B-SHA3, Blake256R14, X11, Cuckatoo31, Cuckatoo32, Equihash, RandomX, SHA3X, Ethash4G, Blake3, zkSNARK, Kadena, NexaPow, XPHash).
`hardwareCost`	No	Upfront hardware cost in USD used for estimated payback days.
`powerSources`	No	Which legs of the site calculator to use. solar=true uses solarW during Peak Sun Hours; battery=true uses leftover solar stored in batteryCapacity at night; grid=true keeps the miner running 24h on leftover grid kWh. solar=true + grid=true + battery=false is "solar by day, grid at night". If grid=false the miner only runs while solar or battery energy lasts (runtimeHours < 24).
`preferredCoin`	No	Target coin when an algorithm supports more than one (BTC/BCH/QUAI, SC/BTCB2, BTCB2/SC, ZEC/ARRR, ETC/OCTA/ETHW/QKC, DCR/SCP). Blake2B-SHA3 is HNS only; Cuckatoo31 is MWC only; Cuckatoo32 is GRIN only. Scrypt reports LTC/DOGE (merged). When omitted, the most profitable supported coin is used except Ethash4G, which defaults to ETC.
`batteryCapacity`	No	Battery storage in kWh (20 = 20 kWh). Only used when powerSources.battery is true (passing batteryCapacity without powerSources turns battery on). Excess daytime solar charges the battery; the battery covers night hours before grid.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description adds real value beyond them: it names the return fields (dailyProfit, dailyCost, solarSavings, runtimeHours, effectiveElecCost), states the figures come from live market inputs, and warns results vary with difficulty/price/power. Gaps remain on auth (API key is only hinted at via the zipCode default profile) and rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the operation and the required/optional split well, but the body is bloated: the HTTP route prefix, a long return-field list, and two sentences of legal disclaimer ('Do your own research', 'not investment, financial, or tax advice') consume space without helping an agent invoke the tool correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter tool with a nested powerSources object and no output schema, the description does the heavy lifting: it enumerates return values, explains the model source, and demonstrates the solar+battery+grid interaction. Only the API-key/auth requirement and error behavior are left unaddressed.

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 carries per-parameter meaning and the baseline is 3. The description reinforces this with a concrete parameter-value example, but it also lists only four optional parameters (solarW, batteryCapacity, zipCode, powerSources) while hardwareCost and preferredCoin are also optional, making the enumeration incomplete.

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?

Names the specific operation and resource: a single-machine home/small-business profitability calculation using a solar/battery/grid leftover-watt model. The scope ('one-machine') and the model make it unmistakable versus the sibling data-retrieval tools (list_miners, get_market, get_rigs).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through a worked example ('3 kW miner on solar by day, grid at $0.15/kWh at night → ...') and a required/optional parameter split, which effectively shows how to call it. But there is no explicit when-to-use/when-not statement, no prerequisites, and no named alternative for related questions (e.g. catalog lookup vs. calculation).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MinerYield tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.