Skip to main content
Glama
Sign In
MCP Tool Server

MCP Tool Server

by nuvolalabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqrt

Calculates the square root of a non-negative number, returning the result for use in mathematical computations or data processing.

Instructions

Square root of a non-negative number.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "number": "<number>"
    },
    "name": "sqrt"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/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 does disclose the key behavioral constraint (input must be non-negative), which is the main failure mode for this tool, but it doesn't say what happens on a negative input (error vs. NaN) or what the return form is. For a pure deterministic math function this is adequate but thin.

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?

One short sentence, front-loaded with the operation, with the constraint attached immediately. No waste.

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?

This is a trivial single-parameter tool with no output schema and no annotations, so the bar is low. The description covers the operation and the input domain; only the negative-input behavior is left unstated.

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 coverage is 0% and the single parameter is named only "number" with type number. The description partially compensates by attaching the non-negative constraint to it, but adds nothing about precision, integer vs. float input, or handling of edge cases like zero.

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 states a specific operation and resource ("Square root") plus a domain constraint ("non-negative number"). It is unambiguous and trivially distinguishable from the arithmetic siblings (echo, add, now_utc), though it doesn't explicitly name those alternatives.

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?

Usage is only implied: an agent infers it should call this when it needs a square root. The non-negativity note hints at a precondition but doesn't say what to do otherwise (e.g., abs first, or expect an error). No alternatives exist among siblings, so the absence of routing guidance is tolerable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools