Skip to main content
Glama
Stauffacher

MCP Server Deepdive Deployment

by Stauffacher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

MCP Server Deepdive Deployment

A Model Context Protocol (MCP) server example that provides basic mathematical operations.

Features

  • add: Add two numbers together

Related MCP server: Learn_MCP Math Server

Installation

From GitHub

Add the following configuration to your MCP settings (e.g., Claude Desktop config):

{
  "mcpServers": {
    "mcp-server-deepdive-deployment": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/Stauffacher/mcpserverexample.git",
        "mcp-server"
      ]
    }
  }
}

Local Development

  1. Clone the repository:

git clone https://github.com/Stauffacher/mcpserverexample.git
cd mcpserverexample

  1. Install dependencies:

uv sync

  1. Run the server:

uv run mcp-server

Project Structure

├── src/
│   └── mcpserver/
│       ├── __init__.py
│       ├── __main__.py      # Entry point
│       └── deployment.py    # MCP tools
├── pyproject.toml           # Project configuration
└── README.md

Requirements

  • Python >= 3.11

  • mcp[cli] >= 1.26.0

License

See LICENSE file for details.

Available Tools

1 tool
addB

Add two numbers

ParametersJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the operation but doesn't disclose behavioral traits like error handling, performance, or limitations (e.g., integer overflow).

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 extremely concise and front-loaded with the essential action. There is no wasted language, making it efficient for quick understanding.

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

Completeness4/5

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

Given the tool's low complexity (simple addition), no annotations, and an output schema (which handles return values), the description is reasonably complete. However, it lacks details on usage context and behavioral aspects.

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?

Schema description coverage is 0%, but the description implies two parameters ('two numbers') without adding details beyond the schema's property names. It doesn't explain parameter roles or constraints, so it meets the baseline for minimal compensation.

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?

The description clearly states the verb ('Add') and resource ('two numbers'), making the purpose unambiguous. However, it doesn't differentiate from siblings (none exist) and could be slightly more specific about the mathematical operation.

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 guidance is provided on when to use this tool versus alternatives. The description only states what it does, not the context or scenarios where it's appropriate.

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.

  1. 1 tool updatev0.1.0
    • First observedadd
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'add' has a clear and distinct purpose of adding two numbers, leaving no room for confusion or misselection by an agent.

Naming Consistency5/5

Since there is only a single tool, naming consistency is inherently perfect. The tool name 'add' follows a simple verb pattern, and with no other tools to compare against, there are no inconsistencies or deviations in naming conventions.

Tool Count2/5

A single tool is generally too few for a server's purpose, as it limits functionality and scope. While the tool 'add' is well-defined, a server with only one tool feels thin and under-scoped, lacking the breadth expected for meaningful agent interactions or domain coverage.

Completeness1/5

The server is severely incomplete, as it only provides a basic arithmetic operation (adding two numbers) without any related functions like subtraction, multiplication, or division. This leaves significant gaps in mathematical or computational workflows, making it inadequate for most practical purposes beyond trivial tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Server Deployment Demo

    AdarshChaudhary03
    F
    license
    C
    quality
    D
    maintenance
    A demonstration MCP server that provides a simple addition tool for learning how to create and deploy servers following the Model-Context-Protocol specification. Serves as a basic example for developers getting started with MCP server development.
    1
    -

  • Fifth Elephant MCP Server

    chaitanyaatlan
    F
    license
    B
    quality
    D
    maintenance
    A demonstration MCP server providing basic tools for returning greetings and performing mathematical addition. It serves as a practical workshop guide for setting up and configuring Model Context Protocol servers from scratch using Python.
    2
    4
    -