Skip to main content
Glama
bahfahh

Basic Math MCP Server

subtraction

Calculate the difference between two numbers by subtracting the second from the first. Use this tool to perform basic subtraction operations in mathematical calculations.

Instructions

Subtract the second number from the first number

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYesFirst number (minuend)
bYesSecond number (subtrahend)

Implementation Reference

  • The handler function performs subtraction (a - b) and returns a formatted text response.
      async ({ a, b }: { a: number; b: number }) => {
        const result = a - b;
        return {
          content: [
            {
              type: "text",
              text: `The subtraction of ${b} from ${a} is: ${result}`
            }
          ]
        };
      }
    );
  • Zod schema defining input parameters 'a' (minuend) and 'b' (subtrahend) as numbers.
    {
      a: z.number().describe("First number (minuend)"),
      b: z.number().describe("Second number (subtrahend)")
    },
  • src/index.ts:44-62 (registration)
    Registration of the 'subtraction' tool with server.tool(), including name, description, input schema, and handler function.
    server.tool(
      "subtraction",
      "Subtract the second number from the first number",
      {
        a: z.number().describe("First number (minuend)"),
        b: z.number().describe("Second number (subtrahend)")
      },
      async ({ a, b }: { a: number; b: number }) => {
        const result = a - b;
        return {
          content: [
            {
              type: "text",
              text: `The subtraction of ${b} from ${a} is: ${result}`
            }
          ]
        };
      }
    );
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. The description only states what the tool does mathematically without addressing behavioral aspects like error handling (e.g., for non-numeric inputs), performance characteristics, or output format. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 a single, clear sentence that directly states the tool's function without any unnecessary words. It is front-loaded with the core action and efficiently communicates the essential information, making it highly concise and well-structured.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (simple arithmetic operation) and the absence of both annotations and an output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits, error handling, and return values, which are important for a complete understanding despite the tool's simplicity.

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 schema description coverage is 100%, with both parameters 'a' and 'b' clearly documented as 'First number (minuend)' and 'Second number (subtrahend)' respectively. The description adds minimal value beyond this, only reinforcing the order of subtraction without providing additional syntax or format details. This meets the baseline for high schema coverage.

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 clearly states the tool's purpose with a specific verb ('Subtract') and identifies the resources involved ('the second number from the first number'). It distinguishes from the sibling 'sum' tool by specifying subtraction rather than addition. However, it doesn't explicitly name the sibling alternative, keeping it from a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (when subtraction is needed) versus the 'sum' sibling tool (when addition is needed), but this is only through contextual inference rather than explicit guidance. No explicit when-not-to-use scenarios or alternative tools are mentioned, making the guidance incomplete.

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/bahfahh/mcptest'

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