Math MCP Server

Overview Schema Source Related Servers Discussions Admin

add

Add two integer numbers together to calculate their sum. This tool performs basic addition for mathematical computations.

Instructions

Adds two integer numbers together.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "add"
  }
}

Input Schema

Name	Required	Description	Default
`a`	Yes
`b`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Removedv0.1.0Feb 2, 2026
First observedJan 12, 2026

TDQS

A3.8/5.0

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 tool 'adds two integer numbers together', which implies a read-only computation, but does not disclose any behavioral traits such as error handling, performance characteristics, or constraints. The description is minimal and lacks 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 a single, efficient sentence that directly states the tool's function without any waste. It is appropriately sized and front-loaded, making it easy for an AI agent to quickly understand the purpose.

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

Completeness4/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), 2 parameters, no annotations, and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the core operation but could benefit from additional context, such as handling of non-integer inputs or error cases, to be fully comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning by specifying that the parameters are 'two integer numbers', which clarifies the expected input types beyond the schema's generic 'number' type. With 0% schema description coverage and 2 parameters, this compensates well, though it could note that 'a' and 'b' correspond to the two numbers being added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific verb ('adds') and resource ('two integer numbers together'), making the purpose explicit. It distinguishes this tool from its siblings (divide, log, multiply, power, subtract) by specifying the addition operation, which is helpful for an AI agent to select the correct mathematical tool.

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 usage for adding integers, but does not explicitly state when to use this tool versus alternatives like 'multiply' or 'subtract'. It provides basic context (adding numbers) but lacks guidance on exclusions or specific scenarios, leaving some ambiguity for the agent in choosing between sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

add