Skip to main content
Glama
islobodan

Crucher MCP

percentage_change

Read-onlyIdempotent

Calculate percentage change between two numbers. Enter the initial and final values to get the percent increase or decrease.

Instructions

Percentage change from A to B. e.g., 50→80 = +60%

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYes
toYes

Implementation Reference

  • cruncher.js:69-77 (registration)
    Tool name listed in the 'standard' tool tier, making it available by default.
    standard: [
        "evaluate_expression",
        "add", "subtract", "multiply", "divide",
        "sqrt", "power", "absolute", "modulo", "factorial",
        "logarithm", "natural_log", "get_constant",
        "sine", "cosine", "tangent", "asin", "acos", "atan",
        "set_angle_mode", "get_angle_mode",
        "sum", "avg", "min", "max", "count", "variance", "std_dev",
        "percentage_of", "percentage_change", "percentage_reverse",
  • Input schema/tool definition for percentage_change: accepts 'from' and 'to' (both numbers, both required).
    {
        name: "percentage_change",
        annotations: {
            title: "Percentage Change",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
        },
        description:
            "Percentage change from A to B. e.g., 50→80 = +60%",
        inputSchema: {
            type: "object",
            properties: {
                from: { type: "number" },
                to: { type: "number" },
            },
            required: ["from", "to"],
        },
    },
  • Handler function that computes percentage change from 'from' to 'to': ((to - from) / from) * 100. Throws if 'from' is zero.
    percentage_change: ({ from, to }) => {
        // % change from A to B: ((to - from) / from) * 100
        if (from === 0)
            throw new Error("Cannot calculate percentage change from zero.");
        return ((to - from) / from) * 100;
    },
  • Listed in MAIN_THREAD_TOOLS set, meaning it runs synchronously on the main thread without worker overhead.
        "percentage_of", "percentage_change", "percentage_reverse",
        // Math one-liners
        "power", "sqrt", "logarithm", "natural_log", "absolute",
        // Constant lookup
        "get_constant",
        // Memory recall (single variable read)
        "memory_recall",
        // Unit conversion
        "convert_unit",
    ]);
Behavior3/5

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

Annotations already mark the tool as read-only, non-destructive, and idempotent. Description adds no further behavioral context beyond the example, which is acceptable for a simple calculation but does not enhance transparency beyond annotations.

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?

Extremely concise: one sentence and an example. No filler or redundant information. Every word contributes to understanding.

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?

For a simple two-parameter calculation, the description with example is nearly complete. It implies the result format (percentage with sign) but does not specify whether the output is a string or number. Slight gap in output specification.

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?

With 0% schema description coverage, the description partially compensates by mapping 'from' and 'to' to 'A' and 'B' in the example. However, it does not explicitly define the meaning of each parameter, leaving some ambiguity.

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?

Description clearly specifies 'percentage change from A to B', indicating a calculation between two numbers. The example further clarifies the operation, distinguishing it from sibling tools like percentage_of or absolute.

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?

No explicit guidance on when to use this tool versus alternatives like percentage_of or percentage_reverse. The example implies use for comparing two values but lacks context or exclusion criteria.

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