Skip to main content
Glama
Yoshua-Carrera

Python MCP Server

Python MCP Server

This is a simple demonstration of a fastmcp server and client.

Setup and Installation (with uv)

This project uses uv for environment and dependency management.

  1. Create the virtual environment:

    uv venv
  2. Activate the virtual environment:

    source .venv/bin/activate
  3. Install the dependencies:

    uv pip sync pyproject.toml

Related MCP server: Fast MCP Local

Usage (with uv)

Make sure your virtual environment is activated before running these commands.

  1. Run the MCP server:

    uv run python server.py

    The server will start on localhost:8000.

Usage for gemini

  1. Configue Gemini CLI Add the following configuration on ~/.gemini/settings.json

    {
      "security": {
        "auth": {
          "selectedType": "oauth-personal"
        }
      },
      "mcpServers": {
        "serverName": {
          "command": "/home/<USER>/.local/bin/uv",
          "args": [
            "--directory",
            "/home/<USER>/code/python-mcp-server",
            "run",
            "server.py"
          ]
        }
      }
    }

    And yes, the home directory can't be summarized to just "~"

  2. Th server does not need to be running simply run Gemini CLI:

    gemini

    From there, you will be able to know if the MCP has been adopted by running the command /mcp list. You should see the tools listed there, similar to this:

    ℹConfigured MCP servers:
    
      🟢 serverName - Ready (2 tools)
        Tools:
        - addNumbers
        - greet
    
    
      💡 Tips:
        • Use /mcp desc to show server and tool descriptions
        • Use /mcp schema to show tool parameter schemas
        • Use /mcp nodesc to hide descriptions
        • Use /mcp auth <server-name> to authenticate with OAuth-enabled servers
        • Press Ctrl+T to toggle tool descriptions on/off

    In this example you will be able to ask Gemini to greet you or add numbers, as long as you provide enough context to fill in the arguments. If you do not provide arguments, Gemini will ask for more information.

    Once all the arguments are provided, Gemini will ask for confirmation before the MCP is hit, and only then will it execute the logic.

Available Tools

2 tools
addNumbersD
ParametersJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

greetD
ParametersJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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. 2 tool updates
    • First observedaddNumbers
    • First observedgreet

TDQS

D1.5/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: addNumbers performs a mathematical operation, while greet handles a social interaction. There is no overlap or ambiguity between them, making misselection unlikely.

Naming Consistency2/5

The naming is inconsistent: addNumbers uses camelCase, while greet uses lowercase. There is no predictable pattern across the set, though both names are readable individually.

Tool Count2/5

With only 2 tools, the server feels thin and under-scoped for a general-purpose Python MCP server. This minimal set suggests limited functionality that may not cover typical Python-related tasks.

Completeness1/5

The tool surface is severely incomplete for a Python server domain. It lacks basic operations like code execution, file handling, or library management, leaving obvious gaps that will cause agent failures in practical scenarios.

Maintenance

ActivityInactive
ResponsivenessSyncing

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

  • A
    license
    Not graded
    quality
    D
    maintenance
    A minimal FastMCP server implementation that provides basic mathematical and greeting tools. Enables users to perform simple operations like adding numbers and greeting people by name through a lightweight MCP interface.
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    A demonstration MCP server built with FastAPI that provides basic mathematical operations and greeting services. Integrates with Gemini CLI to showcase MCP protocol implementation with simple REST endpoints.
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    A minimal demonstration MCP server that provides basic mathematical addition and greeting functionality, serving as a template for building and deploying FastMCP servers.
    -

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/Yoshua-Carrera/python-mcp-server'

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