Skip to main content
Glama
tresor4k

macalc

calculate_mining_profitability

Compute crypto mining profitability after electricity costs. Enter hashrate, power, kWh price, network difficulty, and coin price to get daily and monthly net profit for evaluating mining ROI.

Instructions

Compute crypto mining profitability after electricity costs. Use for miners evaluating ROI. Inputs: hashrate, power W, kWh price, network difficulty, coin price. Returns daily/monthly net profit. See list_bundles for related 'crypto' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashrate_mhsYesMining hashrate in MH/s
power_wattsYesMining hardware power consumption in watts
electricity_cost_kwhYesElectricity cost per kWh in fiat currency
block_rewardNoBlock reward in coins (default 3.125 BTC post-halving)
network_difficultyYesCurrent network difficulty
coin_price_usdYesCurrent coin price in USD

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

No annotations provided, so description carries full burden. It states returns daily/monthly net profit, but does not disclose any behavioral traits like real-time data, caching, or nondestructive nature. Adequate but minimal.

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

Conciseness5/5

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

Three sentences: purpose, user scenario with ROI, inputs/outputs, and reference to related tools. Front-loaded and every sentence earns its place.

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?

Given the presence of an output schema and many sibling tools, the description is fairly complete: it covers purpose, inputs, outputs, and alternative tools. Could mention output currency or units but schema likely fills that gap.

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?

Input schema has 100% description coverage, so parameters are already well-defined. Description lists inputs but adds no new meaning beyond the schema. Baseline score of 3 is appropriate.

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 clearly states 'Compute crypto mining profitability after electricity costs' with a specific verb and resource. It distinguishes from sibling calculators by mentioning electricity cost and ROI focus, and references a related bundle for more context.

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

Usage Guidelines4/5

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

Explicitly targets miners evaluating ROI. The mention of 'See list_bundles for related crypto calculators' guides the agent to alternatives. Does not explicitly say when not to use, but the scenario is well-defined.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server