Skip to main content
Glama
Sign In
mcp-tool-builder

mcp-tool-builder

by hanweg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_bitcoin_price

Retrieve current Bitcoin price in USD from the CoinGecko API for real-time cryptocurrency tracking and financial analysis.

Instructions

Gets current Bitcoin price in USD from CoinGecko API

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • tools/get_bitcoin_price.py:2-10 (handler)
    The handler function that executes the tool logic: fetches the current Bitcoin price in USD from CoinGecko API using urllib and json, formats it, and returns the result or an error message if fetch fails.
    def get_bitcoin_price():
    from urllib import request, error
    import json
    try:
        with request.urlopen('https://api.coingecko.com/api/v3/simple/price?ids=bitcoin&vs_currencies=usd') as response:
            data = json.loads(response.read())
            return f"Current Bitcoin price: ${data['bitcoin']['usd']:,.2f}"
    except:
        return "Error: Unable to fetch Bitcoin price"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the data source (CoinGecko API) but doesn't describe potential rate limits, error conditions, response format, or whether this is a real-time or cached price. For a tool that fetches external data, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that communicates the essential information without any wasted words. It's appropriately sized for a simple tool with no parameters and gets straight to the point about what the tool does.

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

Completeness3/5

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

For a simple tool with no parameters and no output schema, the description covers the basic purpose adequately. However, without annotations and with external API dependencies, it should ideally mention response format, potential limitations, or error handling to be more complete for agent use.

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 tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's core functionality without unnecessary detail.

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

Purpose5/5

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

The description clearly states the specific action ('Gets'), resource ('current Bitcoin price'), and source ('from CoinGecko API'), with the currency unit ('in USD') specified. It distinguishes itself from sibling tools like get_weather_forecast by focusing on cryptocurrency pricing rather than weather data.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or contextual constraints. It simply states what the tool does without indicating appropriate use cases or limitations.

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