Skip to main content
Glama
joeguo911

MCP Demo Server

by joeguo911

add

Calculate the sum of two numbers by inputting numerical values for addition operations.

Instructions

Add two numbers together

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYesFirst number to add
bYesSecond number to add

Implementation Reference

  • demo.ts:94-105 (handler)
    Handler logic for the 'add' tool: extracts parameters a and b, computes their sum, and returns a text response with the result.
    if (name === "add") {
      const { a, b } = args as { a: number; b: number };
      const result = a + b;
      return {
        content: [
          {
            type: "text",
            text: `The sum of ${a} and ${b} is ${result}`,
          },
        ],
      };
    }
  • demo.ts:25-42 (schema)
    Schema definition for the 'add' tool, including name, description, and input schema with required number parameters a and b.
    {
      name: "add",
      description: "Add two numbers together",
      inputSchema: {
        type: "object",
        properties: {
          a: {
            type: "number",
            description: "First number to add",
          },
          b: {
            type: "number",
            description: "Second number to add",
          },
        },
        required: ["a", "b"],
      },
    },
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 of behavioral disclosure. It states the action ('add') but doesn't describe any behavioral traits such as error handling, performance characteristics, side effects, or output format. For a tool with no annotations, this is a significant gap in transparency.

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 ('Add two numbers together')—a single sentence with zero waste. It's front-loaded with the core purpose, making it easy for an agent to parse quickly. Every word earns its place by directly conveying the tool's function.

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

Completeness2/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 lacks information on behavioral aspects (e.g., what happens with non-numeric inputs, overflow handling) and output expectations. While the schema covers parameters well, the description doesn't compensate for missing annotations or output details, leaving gaps for agent understanding.

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?

The input schema has 100% description coverage, with clear parameter descriptions ('First number to add', 'Second number to add'). The description adds no additional meaning beyond what the schema provides, as it only restates the tool's purpose without detailing parameter usage or constraints. Baseline 3 is appropriate given the schema does the heavy lifting.

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 together' clearly states the tool's function with a specific verb ('add') and resource ('two numbers'). It distinguishes from sibling tools like 'calculate' (which might do more complex operations) and 'greet' (which is unrelated). However, it doesn't explicitly differentiate from potential sibling arithmetic tools beyond naming the 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'calculate' or specify use cases (e.g., for simple addition only). There's no context about prerequisites, limitations, or when not to use it, leaving the agent to infer usage from the tool name alone.

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/joeguo911/mcp-demo'

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