Calculator MCP

Overview Schema Source Related Servers Discussions Admin

sqrt

Calculate the square root of any number to solve mathematical problems involving root extraction and numerical analysis.

Instructions

计算平方根

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

Name	Required	Description	Default
`number`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Implementation Reference

calculator.py:39-41 (handler)
The handler function implementing the 'sqrt' tool. It takes a float 'number' and returns its square root using math.sqrt.
```
def sqrt(number: float) -> float:
    """计算平方根"""
    return math.sqrt(number)
```
calculator.py:38-38 (registration)
The @mcp.tool() decorator registers the sqrt function as a tool in the FastMCP server.
```
@mcp.tool()
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. '计算平方根' only states what the tool does, not how it behaves. It doesn't mention error handling (e.g., for negative inputs), performance characteristics, side effects, or output format. This leaves critical behavioral traits undocumented.

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 - a single phrase that directly states the tool's purpose. There's zero wasted language or unnecessary elaboration. It's perfectly front-loaded with the essential information.

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 mathematical simplicity and the presence of an output schema, the description is minimally adequate. However, with no annotations and 0% schema description coverage, it should provide more context about input constraints and behavioral characteristics. The output schema helps, but the description doesn't prepare the agent for potential errors or edge cases.

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?

The schema has 0% description coverage, so the description must compensate. '计算平方根' implies a number parameter but adds no semantic meaning beyond what's obvious from the tool name. It doesn't specify constraints (e.g., must be non-negative), units, or typical ranges. The single parameter remains largely undocumented.

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) clearly states the tool's function with a specific verb and resource. It distinguishes from siblings like 'add' or 'multiply' by specifying the mathematical operation. However, it doesn't explicitly mention that it operates on a single number parameter, which would make it fully distinct from all siblings.

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. It doesn't mention when to choose sqrt over power (which could also calculate roots) or other mathematical operations. There's no context about input constraints (e.g., non-negative numbers) 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.

Deploy Server