Skip to main content
Glama
zhangzhefang-github

MCP Add Server

add

Calculate the sum of two numbers by providing two numerical inputs. This tool performs basic addition operations for mathematical computations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes第一个加数
bYes第二个加数

Implementation Reference

  • The async handler function for the 'add' tool. It receives arguments a and b, computes their sum, logs the process, and returns a standardized text content response with the result.
    }, async ({ a, b }) => {
      console.log(`Tool 'add' called with arguments: a=${a}, b=${b}`); // 日志3: 工具调用及参数
      const sum = a + b;
      console.log(`Tool 'add' - calculated sum: ${sum}`); // 日志4: 计算结果
      return {
        content: [{
          type: "text",
          text: `结果是:${sum}`
        }]
      };
    });
  • Input schema for the 'add' tool using Zod, defining 'a' and 'b' as required number parameters with Chinese descriptions.
    a: z.number().describe("第一个加数"),
    b: z.number().describe("第二个加数")
  • src/server.js:14-27 (registration)
    Registration of the 'add' tool on the McpServer instance, including input schema and handler function.
    server.tool("add", {
      a: z.number().describe("第一个加数"),
      b: z.number().describe("第二个加数")
    }, async ({ a, b }) => {
      console.log(`Tool 'add' called with arguments: a=${a}, b=${b}`); // 日志3: 工具调用及参数
      const sum = a + b;
      console.log(`Tool 'add' - calculated sum: ${sum}`); // 日志4: 计算结果
      return {
        content: [{
          type: "text",
          text: `结果是:${sum}`
        }]
      };
    });
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.

Install Server

Other Tools

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/zhangzhefang-github/mcp-add-server'

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