Skip to main content
Glama
mcp-tool-builder

mcp-tool-builder

by hanweg

WORK IN PROGRESS - USE WITH CAUTION - Windows

MCP Tool Builder

An MCP server that empowers LLMs to dynamically create new tools through MCP clients such as Claude Desktop.

Features

  • Create new tools by describing them in natural language

    • Requires client restart to use new tools (Claude Desktop)

  • New tools are saved as python scriptlets in ...\mcp-tool-builder\tools

  • New tool definitions are saved in ...\mcp-tool-builder\tools\tools.json

Related MCP server: my-mcp-server

Example tools included at installation

  • get_bitcoin_price: Fetches current Bitcoin price from CoinGecko

  • get_weather_forecast: Gets weather for US ZIP codes (uses geopy)

Creating New Tools

Use the create_tool command in Claude Desktop (or suggest strongly!!) to create new tools dynamically

Installation

  1. Clone this repository

  2. Install dependencies:

cd mcp-tool-builder
uv venv
.venv\Scripts\activate
uv pip install -e .

Usage with Claude Desktop

Add to claude_desktop_config.json:

{
    "mcpServers": {
        "tool-builder": {
            "command": "uv",
            "args": [
                "--directory", 
                "PATH_TO\\mcp-tool-builder",
                "run",
                "tool-builder"
            ]
        }
    }
}

Screenshot 2024-12-24 105318

image

Available Tools

4 tools
create_toolC

Create a new Python tool with specified functionality

Inputs: tool_name (required), description (required), code (required).

get_bitcoin_priceA

Gets current Bitcoin price in USD from CoinGecko API

Inputs: no named parameters.

get_weather_forecastC

Retrieves weather forecast for a given ZIP code using NWS API

Inputs: zip_code (required).

list_available_toolsB

List all currently available tools

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools have distinct purposes (tool creation, Bitcoin price, weather forecast, tool listing), but the domain is unclear—'create_tool' and 'list_available_tools' suggest a tool management server, while the other two are unrelated utilities. This mismatch could confuse agents about the server's scope, though individual tools are not directly overlapping.

    Naming Consistency4/5

    Three tools follow a consistent verb_noun pattern (create_tool, get_bitcoin_price, get_weather_forecast), but 'list_available_tools' uses 'list' instead of 'get', breaking full consistency. Overall, naming is mostly predictable and readable with only minor deviation.

    Tool Count3/5

    With 4 tools, the count is reasonable for a small utility set, but it feels thin for a 'tool-builder' server that might imply more comprehensive tool management. The inclusion of unrelated utilities (Bitcoin, weather) makes the scope ambiguous, affecting appropriateness.

    Completeness2/5

    If the domain is tool management, there are significant gaps: no update, delete, or test tools, and the unrelated utilities don't fit. If it's a general utility server, coverage is sparse and random. In either case, the surface is incomplete for coherent agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers