Scientific Calculator

Complex Number Calculator

calculator_complex

Read-only

Complex arithmetic and ops on a+bi (add/sub/mul/div/pow/sqrt/conj/|z|/arg/re/im).

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": {
      "operation": "<operation>",
      "a": "<a>"
    },
    "name": "calculator_complex"
  }
}

Input Schema

Name	Required	Description
`a`	Yes	First complex value.
`b`	No	Second complex value (binary ops).
`exponent`	No	Exponent for power.
`operation`	Yes	add\|subtract\|multiply\|divide\|power\|sqrt\|conjugate\|magnitude\|argument\|real\|imag

Output Schema

Name	Required	Description	Default
`result`	No
`operation`	No
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds the supported operation scope and a+bi notation, but does not discuss result format, error handling, or edge cases; with annotations present, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler. The only minor inefficiency is the slightly redundant phrase 'arithmetic and ops' and dense abbreviations such as conj, pow, and re/im.

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?

Given the low-complexity calculator behavior, full schema description coverage, and an output schema, the description covers the essential operation scope. It does not need to explain return values, but it could say more about when the tool is preferred over sibling complex-number tools.

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%, so the schema already documents parameters such as a, b, exponent, and operation. The description lists operation abbreviations and confirms a+bi input, but adds little beyond the schema's own examples and parameter descriptions.

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 resource (complex numbers) and enumerates the arithmetic operations supported. It is clear what the tool does, but it does not explicitly distinguish itself from nearby siblings such as calculator_complex_convert or calculator_magnitude.

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 operation list implies usage, but there is no explicit guidance on when to choose this tool over alternatives like calculator_complex_convert or calculator_magnitude. No exclusions or selection conditions are provided.

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.