Skip to main content
Glama

min

Determine the smallest number in a given list of numerical values using this mathematical tool, designed to simplify accurate calculations for precise analysis and problem-solving.

Instructions

Finds the minimum value from a list of numbers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numbersYesArray of numbers to find the minimum of

Implementation Reference

  • src/index.ts:182-193 (registration)
    Registration of the 'min' tool, including description, input schema, and handler function that delegates to Statistics.min and returns the result as text content.
    mathServer.tool("min", "Finds the minimum value from a list of numbers", {
        numbers: z.array(z.number()).describe("Array of numbers to find the minimum of")
    }, async ({ numbers }) => {
        const value = Statistics.min(numbers)
    
        return {
            content: [{
                type: "text",
                text: `${value}`
            }]
        }
    })
  • Static method in Statistics class that computes the minimum value using Math.min spread operator on the numbers array.
    static min(numbers: number[]) {
        const minValue = Math.min(...numbers);
    
        return minValue
    }
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 only states what the tool does ('Finds the minimum value') without addressing behavioral traits like error handling (e.g., empty lists, non-numeric elements), performance considerations, or output format. This is inadequate for a tool with no annotation coverage.

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 purpose with zero waste. It is appropriately sized and front-loaded, making it easy to understand at a glance without unnecessary elaboration.

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 (single parameter, no output schema, no annotations), the description is minimally adequate but lacks completeness. It does not explain return values (e.g., what happens with empty lists) or behavioral context, which is needed since annotations are absent. A score of 3 reflects this basic sufficiency with clear gaps.

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?

Schema description coverage is 100%, with the parameter 'numbers' fully documented in the schema as 'Array of numbers to find the minimum of'. The description adds no additional meaning beyond this, such as examples or constraints (e.g., minimum list length). Baseline 3 is appropriate since the schema does the heavy lifting.

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 action ('Finds') and resource ('minimum value from a list of numbers'), distinguishing it from siblings like 'max' (which finds the maximum) and 'mean' (which calculates the average). It precisely conveys the tool's function without ambiguity.

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

Usage Guidelines4/5

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

The description implies usage for finding minimum values in numerical lists, providing clear context. However, it does not explicitly state when to use this tool versus alternatives like 'max' or 'median', or any exclusions (e.g., handling non-numeric inputs). This leaves some guidance gaps compared to explicit sibling differentiation.

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

Related 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/EthanHenrickson/math-mcp'

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