Skip to main content
Glama
islobodan

Crucher MCP

add

Read-onlyIdempotent

Add two numbers to obtain their total sum. Performs basic arithmetic addition.

Instructions

Adds two numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Implementation Reference

  • The tool handler for 'add' — calls safeMath.add(a, b) to sum two numbers.
    add: ({ a, b }) => safeMath.add(a, b),
  • The input schema for 'add' tool: definition of parameters 'a' and 'b' (both type: number).
    // --- Basic Arithmetic (use evaluate_expression for complex math) ---
    {
        name: "add",
        annotations: {
            title: "Add",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
        },
        description:
            "Adds two numbers.",
        inputSchema: {
            type: "object",
            properties: { a: { type: "number" }, b: { type: "number" } },
            required: ["a", "b"],
        },
    },
  • cruncher.js:70-73 (registration)
    Tool name 'add' listed under minimal, standard, and full tool tiers in TOOL_TIERS.
    // Minimal: math primitives + evaluate_expression (5 tools)
    minimal: [
        "evaluate_expression", "add", "subtract", "multiply", "divide",
    ],
  • safeMath.add helper function that performs integer-scaling arithmetic to avoid floating-point errors.
    const safeMath = {
        add: (a, b) => {
            const d1 = countDecimals(a);
            const d2 = countDecimals(b);
            const maxDecimals = Math.max(d1, d2);
            const multiplier = Math.pow(10, maxDecimals);
            return (
                (Math.round(a * multiplier) + Math.round(b * multiplier)) /
                multiplier
            );
        },
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety profile. The description adds no additional behavioral context (e.g., return value), but is not contradictory.

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 sentence of three words, containing no unnecessary information. It is maximally concise for a simple operation.

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 no output schema, the description should imply the return behavior (e.g., the sum). It does not, so the agent lacks assurance about what the tool produces.

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

Parameters2/5

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

Schema coverage is 0%, meaning parameter descriptions are absent. The description only says 'Adds two numbers' without elaborating the role of parameters a and b beyond their numeric type.

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 'Adds two numbers' is a specific verb+resource statement. It clearly distinguishes from siblings like multiply, subtract, etc., which perform different operations.

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?

No guidance is provided on when to use this tool versus alternatives like sum or other arithmetic operations. The agent receives no context about preferred scenarios.

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/islobodan/cruncher-mcp'

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