calculator_mcp

power

Calculate the result of raising a base number to a given exponent. Use this for exponentiation, powers, and repeated multiplication in math expressions.

Instructions

Calculate base raised to the power of exponent (乘方).

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": {
      "base": "<base>",
      "exponent": "<exponent>"
    },
    "name": "power"
  }
}

Input Schema

Name	Required	Description	Default
`base`	Yes
`exponent`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, but this is a pure, deterministic arithmetic function with no side effects, so the disclosure burden is low. The description does not mention edge cases (negative base with fractional exponent, overflow, complex results), which is the main behavioral gap.

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?

A single front-loaded sentence that states the operation precisely, with a brief parenthetical gloss; nothing is wasted and the core action comes first.

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?

For a two-parameter pure function with a sibling set of simple arithmetic tools and an output schema already present, the description covers what an agent needs to select and call it. Only edge-case behavior is left implicit.

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 0%, but the schema titles ('Base', 'Exponent') and the description together make the two parameters' roles clear, and the description adds the mathematical relationship between them. Still, no format, range, or edge-case semantics are provided.

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 gives a specific verb ('Calculate') and an unambiguous mathematical relation ('base raised to the power of exponent'), which an agent can distinguish from siblings like root, multiply, or factorial without opening the schema.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. 'use root for nth roots'). Usage is only implied by the operation itself, which for a math primitive is reasonably self-evident.

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

Deploy Server