Scientific Calculator

Complex Number Converter

calculator_complex_convert

Read-only

Rectangular ↔ polar complex conversion (degrees or radians).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculator_complex_convert"
  }
}

Input Schema

Name	Required	Description	Default
`angle`	No	Polar angle.
`direction`	No	auto\|to_polar\|to_rectangular	auto
`magnitude`	No	Polar magnitude r.
`angle_unit`	No	degrees or radians.	degrees
`rectangular`	No	a+bi form.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.1/5.0

Behavior2/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 little behavioral context beyond the conversion purpose and angle-unit support; it does not explain how direction=auto behaves or how the tool handles incomplete inputs.

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 compact sentence with the operation front-loaded and no wasted text. Its brevity is appropriate for a narrowly scoped conversion tool.

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?

The tool is simple, annotations cover safety, and an output schema exists, so the description does not need to explain return values. However, it omits important input-combination context, such as using rectangular versus magnitude plus angle, and the meaning of direction=auto.

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 all five parameters are documented in the schema. The description mentions degrees or radians, but adds no meaningful semantics beyond the schema for parameters such as direction, rectangular, magnitude, or angle.

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: rectangular-to-polar and polar-to-rectangular complex conversion, including supported angle units. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as calculator_complex, calculator_magnitude, or calculator_convert.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives. An agent can infer that this tool is for complex coordinate conversion, but the description does not explain when to choose it over calculator_complex or other conversion tools.

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.