Skip to main content
Glama
haojiasheng

Notes MCP Server

by haojiasheng

add

Add two numbers together to calculate their sum. Use this tool to perform basic addition operations within the Notes MCP Server.

Instructions

Add two numbers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Implementation Reference

  • Handler function that adds two numbers a and b, returns the result as text.
    async ({ a, b }) => {
      return {
        content: [{ type: "text", text: String(a + b) }],
      };
    }
  • Input schema validating two numbers a and b.
    {
      a: z.number().describe("First number"),
      b: z.number().describe("Second number"),
    },
  • src/index.ts:39-51 (registration)
    Registers the 'Add' tool on the MCP server with name, description, input schema, and handler function.
    server.tool(
      "Add",
      "Add two numbers",
      {
        a: z.number().describe("First number"),
        b: z.number().describe("Second number"),
      },
      async ({ a, b }) => {
        return {
          content: [{ type: "text", text: String(a + b) }],
        };
      }
    );
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Add two numbers' reveals nothing about error handling, rate limits, authentication requirements, or what happens when invalid inputs are provided. It doesn't even specify if this is a read-only or mutation operation. The description provides minimal behavioral context.

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 maximally concise at just three words. It's front-loaded with the core functionality and contains zero wasted words. For such a simple tool, this brevity is appropriate and efficient.

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 a simple mathematical operation with no annotations, no output schema, and 0% schema coverage, the description is inadequate. While the tool's basic purpose is clear, there's no information about return values, error conditions, or operational constraints. The description doesn't provide enough context for reliable tool invocation.

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?

With 0% schema description coverage and two required parameters, the description 'Add two numbers' provides no information about what parameters 'a' and 'b' represent, their data types, constraints, or examples. The description doesn't compensate for the complete lack of schema documentation, leaving parameters semantically undefined.

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 verb ('Add') and resource ('two numbers'), making the purpose immediately understandable. It's specific about what mathematical operation is performed. However, with no sibling tools to differentiate from, it cannot achieve a perfect score of 5.

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, prerequisites, or contextual constraints. It simply states what the tool does without any usage instructions or limitations. This is a basic description that lacks operational guidance.

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/haojiasheng/add-number-mcp'

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