Skip to main content
Glama
Sign In
startmining-mcp

startmining-mcp

by TIBSP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_difficulty_history

Retrieve historical Bitcoin difficulty and hashrate data by date range to analyze mining trends and network changes.

Instructions

Get historical difficulty and hashrate data

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_difficulty_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD)
fromNoStart date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It does not state default time range, output shape, pagination, rate limits, units, or whether results are aggregated, leaving key operational behavior undisclosed.

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?

The description is a single concise phrase and is front-loaded with the action and resource. It is appropriately short, though the brevity contributes to the missing guidance noted elsewhere.

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?

For a historical-data tool with no annotations and no output schema, the description is too sparse. It omits default date behavior, result granularity, and distinctions from closely related sibling tools.

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%, and both from/to parameters have clear YYYY-MM-DD descriptions, so the schema handles parameter semantics adequately. The description adds no additional parameter meaning or constraints beyond the schema.

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

Purpose3/5

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

The description gives a clear verb (Get) and resource (historical difficulty and hashrate data), so the basic purpose is understandable. However, with siblings like get_difficulty, get_hashprice, get_weekly_stats, and get_monthly_averages, it does not distinguish scope or granularity from these alternatives.

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

Usage Guidelines2/5

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

No when-to-use guidance is provided. It does not explain when to choose this historical endpoint instead of get_difficulty, get_hashprice, or get_monthly_averages, nor does it mention default date behavior despite optional from/to parameters.

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

Deploy Server

Other Tools