Skip to main content
Glama

btc-game-theory

Calculate Bitcoin mining game theory metrics: selfish-mining profitability threshold, 51% attack electricity cost, fee vs subsidy split, difficulty trajectory, and Nash equilibrium for honest mining.

Instructions

Bitcoin mining game theory and systems dynamics in one call. Returns: selfish-mining profitability threshold (Eyal-Sirer), 51%-attack electricity cost estimate, fee-vs-subsidy revenue split, difficulty epoch trajectory (expansion / contraction / neutral), Nash-equilibrium state for honest mining, and current epoch progress. Sourced from mempool.space and CoinGecko — no API key required. Use for miner-incentive analysis, network security assessment, and pre-investment regime detection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectivity_gammaNoAssumed fraction of honest miners who extend the selfish chain when block heights are equal (0–1). Higher γ means better-connected selfish miner. Default 0 (worst-case for honest miners).
electricity_kwh_usdNoAssumed electricity cost in $/kWh for 51%-attack cost estimate. Default 0.07.
efficiency_w_per_thNoAssumed ASIC power efficiency in W/TH. Default 20 (representative of modern S21/M60 hardware). Lower = more efficient attackers.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses data sources (mempool.space, CoinGecko) and that no API key is needed, implying a read-only, safe operation.

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?

The description is a single paragraph that efficiently lists outputs and sources, with zero wasted words. It is front-loaded with the core purpose.

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?

Despite having no output schema, the description enumerates all returned values and explains their significance. For a complex tool with 3 parameters, this is complete.

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% and the description adds context beyond each parameter's schema description by explaining their role in the models and providing sensible defaults.

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 uses a specific verb ('Returns') and names multiple concrete metrics (selfish-mining profitability threshold, 51%-attack electricity cost, etc.), clearly distinguishing it from siblings like btc-miner-econ and btc-systems-theory.

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?

The description states explicit use cases ('miner-incentive analysis, network security assessment, pre-investment regime detection') but does not mention when to avoid this tool or suggest alternatives.

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/thebrierfox/the-stall'

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