Skip to main content
Glama
anilvermaspeaks

MCP Basic Create Tool

🧠 MCP Basic Create Tool

A minimal Model Context Protocol (MCP) project demonstrating how to create and register tools using the fastmcp framework.

This repository shows how to build a working MCP server that can expose Python functions as tools for AI clients like Claude Desktop or any other MCP-compatible app.


🚀 Features

  • Simple MCP server setup using FastMCP

  • Example tool implementation (get_weather)

  • Easy to extend with more tools

  • Ready for integration with Claude or ChatGPT (via MCP)


1️⃣ Clone the repository

git clone https://github.com/anilvermaspeaks/mcp-bacis-create-tool.git
cd mcp-bacis-create-tool

 Create and activate a virtual environment
python -m venv basics-mcp


To connect this tool to Claude Desktop, add the following entry inside your Claude configuration file:

Config path:

Windows → %APPDATA%\Claude\claude_desktop_config.json

macOS → ~/Library/Application Support/Claude/claude_desktop_config.json

Add this JSON snippet:

{
  "mcpServers": {
    "mcp-bacis-create-tool": {
      "command": "python",
      "args": [
        "D:/basics-mcp/main.py"
      ],
      "env": {
        "PYTHONPATH": "D:/basics-mcp"
      }
    }
  }
}

## run MCP server(main.py) using custom mcp client(client.py)
  uv run python client.py

Available Tools

1 tool
get_weatherB

Gets the weather for a given location.

Args:
    location (str): The location (city, country, etc.)

Returns:
    str: A short weather description.
ParametersJSON Schema
NameRequiredDescriptionDefault
locationYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, and description does not disclose potential side effects, prerequisites, or error handling. Returns only a string, but no details on API limits or data freshness.

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?

Description is brief and front-loaded with the main action, using a clear docstring format. No unnecessary words.

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?

Tool is simple with one parameter and a string return. Description covers basic usage but omits details like units, time specificity, or error conditions. Output schema exists but description already mentions return type.

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?

Schema has 0% description coverage, but the free-text description explains the parameter as a location string (city, country, etc.), adding useful context beyond the schema's property name and type.

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?

Description clearly states it gets weather for a location, but lacks specificity on whether it's current, forecast, or conditions. With no sibling tools, differentiation is not required.

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?

No explicit guidance on when to use or alternatives, but the purpose is straightforward and no siblings exist. Minimal but adequate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observedget_weather

TDQS

B3.2/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The agent will always select 'get_weather' for weather queries.

Naming Consistency5/5

With only one tool, no naming inconsistencies exist. The name 'get_weather' follows a clear verb_noun pattern.

Tool Count1/5

A single tool is extremely limited for a server named 'MCP Basic Create Tool', which suggests a broader scope. Additionally, the only tool is a weather lookup, not a creation tool, making the count inappropriate.

Completeness1/5

The server provides only a basic weather retrieval tool. For a weather domain, one would expect additional operations like forecast, historical data, or location search, but none are present.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • F
    license
    B
    quality
    D
    maintenance
    A lightweight server that exposes weather-related tools (get_coordinates and get_forecast) using the Modular Command Protocol, designed for integration with AI agents and LLMs.
    2
    -
  • F
    license
    Not graded
    quality
    C
    maintenance
    A basic MCP server implementation using the FastMCP framework that provides utility tools for greetings and mathematical calculations. It is designed to demonstrate tool integration for AI-assisted development workflows like Cline.
    -
  • A
    license
    A
    quality
    B
    maintenance
    A simple MCP server that exposes a get_weather tool to fetch real-time weather for any GPS coordinates using the Open-Meteo API, no API key required.
    1
    21
    ISC

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/anilvermaspeaks/mcp-bacis-create-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server