Skip to main content
Glama
tech-sushant

Calculator MCP Server

by tech-sushant

sqrt

Calculate the square root of any number to solve mathematical problems or verify calculations.

Instructions

Calculate square root of a number

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesNumber to calculate square root of

Implementation Reference

  • Handler logic for the 'sqrt' tool: validates input number is non-negative, computes square root using Math.sqrt, and returns formatted result or error.
    case "sqrt": {
      const { number } = args as { number: number };
      if (number < 0) {
        return {
          content: [
            {
              type: "text",
              text: "Error: Cannot calculate square root of negative number",
            },
          ],
          isError: true,
        };
      }
      const result = Math.sqrt(number);
      return {
        content: [
          {
            type: "text",
            text: `√${number} = ${result}`,
          },
        ],
      };
    }
  • src/index.ts:110-123 (registration)
    Registration of the 'sqrt' tool in the tools array, including name, description, and input schema definition.
    {
      name: "sqrt",
      description: "Calculate square root of a number",
      inputSchema: {
        type: "object",
        properties: {
          number: {
            type: "number",
            description: "Number to calculate square root of",
          },
        },
        required: ["number"],
      },
    },
  • Input schema for the 'sqrt' tool defining the expected 'number' parameter.
    inputSchema: {
      type: "object",
      properties: {
        number: {
          type: "number",
          description: "Number to calculate square root of",
        },
      },
      required: ["number"],
    },
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. It states the basic operation but does not disclose behavioral traits such as error handling for negative inputs, performance characteristics, or output format. This leaves gaps in understanding how the tool behaves beyond the core function.

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 with zero waste. It is front-loaded and directly conveys the tool's purpose without unnecessary details, making it easy for an AI agent to parse quickly.

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 the lack of annotations and output schema, the description is incomplete. It does not address error cases, return values, or usage context, which are important for a mathematical operation tool. This reduces its effectiveness in guiding an AI agent fully.

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?

The input schema has 100% description coverage, with the parameter 'number' clearly documented. The description adds no additional meaning beyond the schema, such as constraints or examples. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 'Calculate square root of a number' clearly states the verb ('calculate') and resource ('square root of a number'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'power' (which could also compute roots), so it falls short of a perfect score.

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. For example, it does not mention using 'power' for other root calculations or specify that this is for non-negative numbers (though implied by the operation). This lack of context reduces its utility for an AI agent.

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/tech-sushant/calculator-mcp'

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