Skip to main content
Glama
FuzzyCZX

MCP Communication Server

by FuzzyCZX

Addition Tool

add

Perform addition of two numbers using the MCP Communication Server, enabling real-time data communication and calculations for client applications.

Instructions

Add two numbers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Implementation Reference

  • The handler function for the 'add' tool. It receives two numbers 'a' and 'b' as input and returns their sum as a text content block.
    async ({ a, b }: { a: number; b: number }) => ({
      content: [{ type: "text", text: String(a + b) }]
    })
  • The input schema for the 'add' tool, defining two required number parameters 'a' and 'b' using Zod validation.
    inputSchema: { a: z.number(), b: z.number() }
  • src/index.ts:48-57 (registration)
    The registration of the 'add' tool using server.registerTool, including title, description, input schema, and inline handler function.
    server.registerTool("add",
      {
        title: "Addition Tool",
        description: "Add two numbers",
        inputSchema: { a: z.number(), b: z.number() }
      },
      async ({ a, b }: { a: number; b: number }) => ({
        content: [{ type: "text", text: String(a + b) }]
      })
    );
Behavior1/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 of behavioral disclosure. The description 'Add two numbers' reveals nothing about behavioral traits such as error handling, performance characteristics, side effects, or return format. It's a minimal statement that doesn't add any context beyond the basic operation.

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 with a single sentence 'Add two numbers' that directly states the purpose without any waste. It's front-loaded and appropriately sized for a simple tool, though this conciseness comes at the cost of completeness.

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?

Given the tool's simplicity (2 parameters, no annotations, no output schema), the description is incomplete. It doesn't cover behavioral aspects, parameter semantics, or usage guidelines. While the operation is straightforward, the description lacks necessary context for an AI agent to understand how to invoke it effectively beyond the basic schema.

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?

The schema description coverage is 0%, meaning the input schema provides no descriptions for parameters 'a' and 'b'. The description 'Add two numbers' adds no meaning beyond what the schema already implies from property names and types. It doesn't explain what 'a' and 'b' represent, their constraints, or usage examples.

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 'Add two numbers' clearly states the tool's purpose with a specific verb ('Add') and resource ('two numbers'). It's unambiguous about what the tool does, though it doesn't explicitly distinguish from the sibling tool 'open_web_page' since they serve completely different domains (mathematics vs. web navigation).

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions for usage. The sibling tool 'open_web_page' is unrelated, so no comparison is needed, but there's still no usage context provided.

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

Related Tools

  • @YuheiNakasaka/arithmetic-mcp-server
  • @wrtnlabs/calculator-mcp
  • @zhangzhefang-github/mcp-add-server
  • @hongsw/hello-mcp
  • @dynstat/mcp-demo
  • @wudongjie/example-mcp-server

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/FuzzyCZX/MCP'

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