Skip to main content
Glama
teamssUTXO

Bitcoin-MCP-Server

get_top1_mining_pool

Identify the leading Bitcoin mining pool by retrieving its name, blocks mined, and dominance percentage over the last 3 months. Use this to assess mining centralization or quickly find the current market leader.

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
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 effectively discloses key behavioral traits: it's a read-only operation (implied by 'get information'), returns detailed metrics in string format, and specifies the time frame (last 3 months) and scope (leading pool only). However, it doesn't mention potential rate limits, authentication needs, or error conditions.

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?

Well-structured and front-loaded: the first sentence states the purpose, followed by output details and usage guidelines. Every sentence adds necessary context without redundancy, making it efficient and easy to parse.

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?

Given the tool's simplicity (0 parameters, output schema exists), the description is complete. It covers purpose, output format, usage scenarios, and differentiation from siblings, providing all needed context for an agent to invoke it correctly without over-explaining.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on output semantics, listing the returned metrics (pool name, slug, blocks mined, dominance percentage, link), which adds value beyond the output 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 the specific action ('get information about the current #1 ranked Bitcoin mining pool') and resource ('based on blocks mined over the last 3 months'), distinguishing it from sibling tools like 'get_mining_pool_by_slug' or 'get_top_10_mining_pools_rank' by focusing exclusively on the top-ranked pool.

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?

Explicitly states when to use this tool ('When you only need to know who currently dominates Bitcoin mining') and when not to use it ('without needing to retrieve data for all top pools'), with clear alternatives implied by sibling tools like 'get_top_10_mining_pools_rank' for broader data.

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-Server'

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