Skip to main content
Glama
Sign In
startmining-mcp

startmining-mcp

by TIBSP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_price_history

Retrieve historical Bitcoin prices by date range and hourly or daily granularity for analysis or charting.

Instructions

Get historical Bitcoin prices

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD)
fromNoStart date (YYYY-MM-DD)
granularityNoData granularity (default: day). For calendar-month averages use get_monthly_averages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/5.0
Behavior2/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, yet it says nothing about read-only semantics, the default granularity of "day", date-range behavior when from/to are omitted, or what the returned series looks like. For an unannotated data tool this is a real gap.

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?

A single front-loaded sentence with zero filler, which is efficient. It is arguably too terse for the information an agent needs, but the sentence itself is well-formed and wastes nothing.

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?

With no annotations and no output schema, the description should at least state defaults and the relationship to get_monthly_averages/get_market_data. It omits both, leaving the agent to infer scope and behavior from the schema alone.

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 the schema already documents from, to, and granularity (including the enum and the get_monthly_averages pointer). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

"Get historical Bitcoin prices" names a specific verb and resource, so the agent knows this retrieves time-series price data. However, it does not differentiate from siblings that also return price/market data, such as get_market_data or get_monthly_averages.

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?

There is no guidance on when to use this tool versus get_market_data, get_monthly_averages, or get_hashprice. The only routing hint ("use get_monthly_averages for calendar-month averages") lives in the schema, not the description.

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