MCP All-in-One Server

by Arnie936

Overview Schema Source Related Servers Discussions Admin

Python

Local

divide

Compute the quotient of two numbers a and b. Returns a divided by b.

Instructions

Divide a by b

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "divide"
  }
}

Input Schema

Name	Required	Description	Default
`a`	Yes
`b`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Implementation Reference

calculator_server/server.py:196-201 (handler)
The divide function is registered as an MCP tool via the @mcp.tool() decorator. It takes two floats a and b, raises ValueError if b is zero (to prevent division by zero), and returns a divided by b.
```
@mcp.tool()
def divide(a: float, b: float) -> float:
    """Divide a by b"""
    if b == 0:
        raise ValueError("Cannot divide by zero")
    return a / b
```
calculator_server/server.py:196-196 (registration)
The @mcp.tool() decorator registers the divide function as an MCP tool on the FastMCP instance.
```
@mcp.tool()
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 16, 2026

TDQS

A4/5.0

Behavior3/5

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

There are no annotations, so the description carries the burden of behavioral disclosure. 'Divide a by b' states the core operation and implies a pure computation, but it does not mention edge cases such as division by zero, error behavior, or output type.

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, front-loaded sentence with no filler. Every word contributes semantic value, and the structure is perfectly sized for the simplicity of the tool.

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?

For a two-parameter pure arithmetic tool, the description plus schema is nearly complete. The output schema likely covers the return shape. The only meaningful missing context is the division-by-zero behavior, which could lead to runtime errors if b is 0.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must provide meaning for the parameters. It clearly establishes that a is the dividend and b is the divisor, making the order and relationship between the two parameters explicit. However, it does not state constraints such as b ≠ 0.

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 uses a specific verb ('Divide') and names the exact resource/operation ('a by b'), which clearly distinguishes it from the sibling tools add, subtract, and multiply. An agent can immediately know this tool computes division and nothing else.

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?

The description implies when to use the tool—whenever division is needed—but it does not explicitly state when not to use it or compare it to the arithmetic siblings. No alternative tools or exclusion conditions are mentioned.

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

Deploy Server