Skip to main content
Glama
teamssUTXO

Bitcoin-MCP-Server

get_top1_mining_pool

Retrieve the current leading Bitcoin mining pool by blocks mined over the last 3 months. Get name, dominance percentage, and details for rapid market analysis.

Instructions

Use this to get information about the current #1 ranked Bitcoin mining pool based on blocks mined over the last 3 months.

Returns detailed metrics in string format for the leading mining pool only:
- Pool name
- Pool slug identifier (used for searching specific pool details)
- Total number of blocks mined in the last 3 months
- Dominance percentage (share of all blocks mined in the 3-month period)
- Link to pool information page

This provides quick access to the most dominant mining pool without needing to retrieve data for all top pools.

Use cases: When you only need to know who currently dominates Bitcoin mining, to check if mining centralization is concerning, or to quickly identify the market leader.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations exist, but the description fully discloses behavior: returns string format with specific metrics, no mention of side effects, and clearly a read-only operation.

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?

Well-structured with a clear opening sentence, bullet list, and use cases. Slightly verbose but each sentence adds information.

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 tool with no parameters and an output schema, the description is complete: explains output format, fields, time range, and use cases. No gaps.

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?

No parameters, so schema coverage is 100%. The description adds value by listing the returned fields, which is helpful beyond the schema.

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 it retrieves info about the #1 ranked Bitcoin mining pool over 3 months. It uses specific verb 'get' and resource 'current #1 ranked Bitcoin mining pool', distinguishing from sibling tools like get_top_10_mining_pools_rank.

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 use cases are provided: when you need to know who dominates or check centralization. It implies not to use when you need all top pools, aligning with sibling tools.

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/teamssUTXO/bitcoin_mcp'

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