Skip to main content
Glama
Sign In
Bitcoin Data MCP Server

Bitcoin Data MCP Server

by myownipgit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_price_data

Retrieve current Bitcoin price and market data, with optional historical timeframe selection.

Instructions

Get current Bitcoin price and market 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_price_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeframeNoTimeframe for historical datacurrent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states a vague action ('get current Bitcoin price and market data') without mentioning that it is read-only, what data fields are included, or any rate limits. The agent lacks essential behavioral context.

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, front-loaded sentence with no wasted words. However, it is overly terse given the complexity of the sibling tools and parameter semantics, sacrificing completeness for brevity.

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?

Despite the tool's simplicity, the description is incomplete. It does not define 'market data', fails to distinguish the tool from 'get_historical_price', and does not specify valid values for the 'timeframe' parameter. Key contextual information is missing.

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?

The input schema has 100% coverage with a single parameter described. The tool description adds no extra meaning beyond the schema's description of 'timeframe'. Since the schema already covers the parameter, a baseline of 3 is appropriate.

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 states 'Get current Bitcoin price and market data', specifying a verb and resource. However, it conflicts with the input schema's 'timeframe' parameter, which suggests historical data can be retrieved, creating ambiguity with the sibling tool 'get_historical_price'. The purpose is vague regarding scope and differentiation.

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 usage guidance is provided. The description fails to indicate when to use this tool versus siblings like 'get_historical_price' or 'get_network_metrics', leaving the agent without context for correct tool selection.

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