Scientific Calculator

Basic Calculator

calculator_basic

Read-only

Use this tool for addition, subtraction, multiplication, or division of two numbers. Handles division by zero with an error.

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>",
      "operation": "<operation>"
    },
    "name": "calculator_basic"
  }
}

Input Schema

Name	Required	Description
`a`	Yes	First operand.
`b`	Yes	Second operand.
`operation`	Yes	Operation: add, subtract, multiply, divide (or +, -, *, /, ×, ÷).

Output Schema

Name	Required	Description	Default
`a`	Yes
`b`	Yes
`result`	Yes
`operation`	Yes
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral detail beyond the annotations: division by zero produces an error. It does not describe precision or output shape, but an output schema exists, reducing the burden.

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 two sentences, front-loaded with the core purpose, and contains no redundant or filler text. Every sentence adds useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter arithmetic tool with full schema coverage, annotations, and an output schema, the description is complete enough to call correctly. It covers the operations and the notable division-by-zero behavior.

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%, and the schema fully documents the two operands and the operation enum with aliases. The description does not add meaning beyond the schema, so the baseline 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 clearly states the resource and operations: addition, subtraction, multiplication, and division of two numbers. It is specific enough to separate this tool from most specialized siblings, though it does not explicitly differentiate itself from broader siblings such as calculator_scientific.

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 phrase 'Use this tool for...' implies the intended use case, but the description gives no explicit when-not guidance and does not name an alternative sibling for overlapping arithmetic functionality. It is adequate but leaves the agent to infer routing.

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

All Scientific Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.