yifanli-mcp-add-demo
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@yifanli-mcp-add-demowhat is the sum of 15 and 27?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
yifanli-mcp-add-demo
A minimal MCP Server built with the official Python MCP SDK.
Features
Runs locally over
stdioExposes one MCP tool:
addCan be launched with
uvx yifanli-mcp-add-demo
Tool
add
Adds two integers and returns the result.
Inputs:
a: integerb: integer
Output:
integer sum
Requirements
Python 3.10+
uvinstalled locally
Run Locally
Use uvx after publishing the package:
uvx yifanli-mcp-add-demoOr run from source in the project directory:
uv run python -m yifanli_mcp_add_demoCherry Studio Config
If you want to connect this server in Cherry Studio with stdio, use:
Command:
uvxArguments:
yifanli-mcp-add-demo
Equivalent JSON-style config:
{
"mcpServers": {
"yifanli-mcp-add-demo": {
"command": "uvx",
"args": ["yifanli-mcp-add-demo"]
}
}
}Package
This project is packaged for publishing to PyPI and local installation via uvx.
Source code lives in:
src/yifanli_mcp_add_demo
Available Tools
1 tooladdA
Add two numbers
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | ||
| b | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description is a pure function with no side effects, and the sole behavior 'Add two numbers' is fully disclosed. With no annotations to contradict, the description provides complete behavioral transparency for this simple operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no unnecessary words; it is front-loaded and earns its place. It communicates everything needed in the most compact form possible.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simple nature and the presence of an output schema (per context signal), the description sufficiently covers the function. There are no complex behaviors, side effects, or conditional logic to document.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description only generically mentions 'two numbers' without explaining the meaning or constraints of parameters a and b. It does not compensate for the lack of schema descriptions, leaving parameter semantics under-specified.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Add' and identifies the resource as 'two numbers', clearly distinguishing it from the sibling arithmetic tools subtract, multiply, and divide. It is unambiguous and precisely states the tool's function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description is concise but does not explicitly state when to use this tool over alternatives; however, the operation is self-evident for the sibling context. It lacks explicit exclusions or alternative guidance, but the clear context of adding numbers implicitly covers the main use case.
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 tool update
v0.1.2- First observed
add
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as adding two numbers, making it distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'add' is simple and follows a verb-based pattern.
One tool is too few for a server's purpose, as it severely limits functionality and suggests an incomplete or trivial implementation. A single addition operation does not justify a full server scope.
The server is severely incomplete, as it only supports adding two numbers with no other arithmetic operations (e.g., subtract, multiply, divide) or related functionalities. This creates significant gaps for any practical use.
Related MCP Connectors
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
