Skip to main content
Glama
Sign In
startmining-mcp

startmining-mcp

by TIBSP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_market_data

Fetch current Bitcoin market and mining data, including price, hashprice, difficulty, and network stats, to monitor live mining economics.

Instructions

Get current Bitcoin market and mining data including price, hashprice, difficulty, and network stats

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_market_data"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a read-only operation and the returned fields are listed, but there is no mention of caching/freshness, rate limits, or auth requirements for what is presumably a live external data fetch.

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?

A single front-loaded sentence that names the resource first and then lists contents; no filler or redundancy.

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

Completeness4/5

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

For a zero-parameter read tool with no output schema, the description adequately enumerates what comes back (price, hashprice, difficulty, network stats). The remaining gap is that it does not clarify the aggregation relationship with overlapping siblings.

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 schema has zero parameters with 100% coverage, and the base case for a no-argument tool is 4. Nothing about invocation needs further clarification.

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

Purpose4/5

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

The description states a specific verb (Get) and resource (current Bitcoin market and mining data) and enumerates the contents: price, hashprice, difficulty, network stats. It is clear, but it never distinguishes itself from siblings like get_hashprice and get_difficulty, which return overlapping subsets of the same data.

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

Usage Guidelines3/5

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

The word 'current' implicitly signals a snapshot rather than history, weakly steering the agent away from get_price_history and get_difficulty_history. However, it never explains when to use this aggregate call versus the narrower get_hashprice/get_difficulty siblings that return the same fields.

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