Skip to main content
Glama
islobodan

Crucher MCP

min

Read-onlyIdempotent

Calculates the minimum value from a list of numbers. Provide an array of numbers to get the smallest one.

Instructions

Minimum of numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numbersYes

Implementation Reference

  • cruncher.js:591-627 (registration)
    Tool 'min' registration in the master tool catalog (toolsAll array). Defines name, annotations, description, and inputSchema requiring an array of numbers.
    {
        name: "median",
        annotations: {
            title: "Median",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
        },
        description: "Median of numbers.",
        inputSchema: {
            type: "object",
            properties: {
                numbers: { type: "array", items: { type: "number" } },
                timeout: { type: "number", minimum: 100, maximum: 60000, description: "Custom timeout in ms (100-60000, default: 3000)" },
            },
            required: ["numbers"],
        },
    },
    {
        name: "min",
        annotations: {
            title: "Minimum",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
        },
        description: "Minimum of numbers.",
        inputSchema: {
            type: "object",
            properties: {
                numbers: { type: "array", items: { type: "number" } },
            },
            required: ["numbers"],
        },
    },
  • Input schema for the 'min' tool: requires an array of numbers.
    inputSchema: {
        type: "object",
        properties: {
            numbers: { type: "array", items: { type: "number" } },
        },
        required: ["numbers"],
    },
  • Handler function for the 'min' tool. Iterates over numbers array to find and return the minimum value. Throws error for empty array.
    min: ({ numbers }) => {
        if (numbers.length === 0)
            throw new Error("Cannot find the minimum of an empty list.");
        let minVal = Infinity;
        for (let i = 0; i < numbers.length; i++) {
            if (numbers[i] < minVal) minVal = numbers[i];
        }
        return minVal;
    },
  • cruncher.js:82-82 (registration)
    'min' listed in the standard tool tier (TOOL_TIERS.standard) — enabled by default.
    "sum", "avg", "min", "max", "count", "variance", "std_dev",
  • 'min' listed in MAIN_THREAD_TOOLS set, meaning it runs in the main thread without worker overhead for performance.
    const MAIN_THREAD_TOOLS = new Set([
        // Angle management
        "set_angle_mode", "get_angle_mode",
        // Trigonometry (instant Math calls)
        "sine", "cosine", "tangent", "asin", "acos", "atan",
        // Cache management
        "cache_clear", "cache_info",
        // Simple stats (zero-cost)
        "count", "min", "max", "variance", "std_dev",
        // Percentage
        "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 declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds no behavioral details beyond the basic operation, such as handling of empty arrays or non-numeric values, which would be useful.

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 extremely concise at four words, front-loading the purpose with no wasted text. Every word is essential.

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?

The tool has one parameter and no output schema, yet the description omits edge cases (e.g., empty array, non-numeric items) and the return type. Given the simplicity, more context would improve completeness.

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 description coverage is 0%, and the description does not elaborate on the 'numbers' parameter beyond its name. The parameter is self-explanatory, but with low coverage the description should compensate, which it doesn't.

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 'Minimum of numbers.' clearly states the tool computes the minimum value from a set of numbers. It's specific and distinct from siblings like 'max' or 'avg', though it could be expanded slightly to avoid ambiguity with other types of minimums.

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 (e.g., 'min' vs 'max' or 'min' vs 'avg'), nor any context about prerequisites or typical use cases.

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