calculator

complex_add

complex_add

Add two complex numbers by providing real and imaginary components for each number. This tool calculates the sum of complex values in mathematical operations.

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": {
      "a_real": "<a_real>",
      "a_imag": "<a_imag>",
      "b_real": "<b_real>",
      "b_imag": "<b_imag>"
    },
    "name": "complex_add"
  }
}

Input Schema

Name	Required	Description	Default
`a_real`	Yes
`a_imag`	Yes
`b_real`	Yes
`b_imag`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 5, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the mathematical operation but doesn't disclose behavioral traits like error handling (e.g., for invalid inputs), performance characteristics, or output format. For a mathematical tool with zero annotation coverage, this leaves significant gaps.

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, efficient sentence in Chinese that directly states the purpose. It's appropriately sized and front-loaded with zero wasted words, making it easy to parse quickly.

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

Completeness2/5

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

Given no annotations, no output schema, and 0% schema description coverage for a 4-parameter tool, the description is incomplete. It lacks details on parameter meanings, output format, error conditions, or usage context, leaving the agent with insufficient information for reliable invocation.

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?

Schema description coverage is 0%, so the description must compensate. It mentions '两个复数' (two complex numbers) which implies four parameters (real and imaginary parts), but doesn't explain the parameter names (a_real, a_imag, etc.) or their semantics. The description adds minimal value beyond what's inferable from the schema.

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 '计算两个复数的和' (calculates the sum of two complex numbers) clearly states the verb (calculate sum) and resource (complex numbers). It distinguishes from sibling tools like 'complex_subtract' by specifying addition, but doesn't explicitly differentiate from generic 'add' which might handle other data types.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention when complex addition is needed versus other mathematical operations, nor does it reference sibling tools like 'complex_subtract' or 'add' for context.

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

Deploy Server