my-mcp-server

calculator

Perform addition, subtraction, multiplication, or division on two numbers and get the result.

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": {
      "firstNumber": "<firstNumber>",
      "secondNumber": "<secondNumber>",
      "operator": "<operator>"
    },
    "name": "calculator"
  }
}

Input Schema

Name	Required	Description
`operator`	Yes	수행할 연산자 (+, -, *, /)
`firstNumber`	Yes	첫 번째 숫자
`secondNumber`	Yes	두 번째 숫자

Output Schema

Name	Required	Description	Default
`result`	Yes	계산 결과

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states it performs arithmetic and returns result, omitting edge cases (e.g., division by zero, floating-point precision), side effects (none), or permissions needed. Fails to adequately describe behavior beyond the bare operation.

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 concise sentence that is front-loaded and easy to parse. However, it omits important behavioral details, slightly reducing its overall utility while remaining efficient.

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?

Given low complexity and presence of output schema, the description is minimally adequate but does not mention return format, statelessness, or safety. For a tool with no annotations, more detail would improve completeness.

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 coverage is 100% with clear parameter descriptions and an enum for operator. The description adds no additional meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 clearly states it performs arithmetic operations on two numbers and returns the result, which is a specific verb-resource pair. It distinguishes from sibling tools that are unrelated to arithmetic.

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 use for basic arithmetic, but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions (e.g., division by zero). No context about prerequisites or limitations.

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

Deploy Server