Skip to main content
Glama
Sign In

Mempool Space

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Mining Pools

mining_pools
Read-onlyIdempotent

Block share by mining pool.

Input Schema

NameRequiredDescriptionDefault
periodNo24h | 3d | 1w | 1m | 3m | 6m | 1y | 2y | 3y | all (default 1w)
networkNoWhich Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet.mainnet

Output Schema

NameRequiredDescriptionDefault
poolsNoMining pool block statistics
lastEstimatedUpdateNoLast update timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / network / default
      Added value: +"mainnet"
    • addedInput schema / properties / network / description
      Added value: +"Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what \"Bitcoin\" means in an ordinary question. \"bitcoin\" and \"btc\" are accepted as aliases for mainnet."
    • addedInput schema / properties / network / enum
      Added value: +[
+  "mainnet",
+  "testnet",
+  "signet",
+  "liquid"
+]
  2. First observed

TDQS

C2/5.0
Behavior2/5

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

Annotations already indicate read-only and idempotent behavior, but the description adds no extra behavioral context (e.g., data freshness, exclusion of unknown pools) to guide the agent.

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

Conciseness2/5

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

The description is extremely short (3 words) but at the cost of clarity; it does not provide enough information to be useful despite being front-loaded.

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

Completeness2/5

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

Given the tool's simplicity and presence of an output schema, the description is still too sparse to convey the tool's purpose and scope adequately.

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 fully documents both parameters. The description adds no additional meaning beyond what is in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Block share by mining pool.' is vague; it does not clearly state that the tool returns the distribution of block contributions across pools, nor does it distinguish from related tools like hashrate.

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

Usage Guidelines1/5

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

No usage context is provided; there is no indication of when to use this tool over alternatives (e.g., hashrate) or any prerequisites.

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

All Mempool Space toolsInspect
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.

Resources