Skip to main content
Glama

engineering.torque_rotational_power

Read-onlyIdempotent

Calculates rotational power in watts from torque in N·m and angular velocity in rad/s. Use it to convert rpm to ω first, since multiplying torque by angular velocity directly yields incorrect results.

Instructions

회전 일률 P = τ·ω (W)를 계산한다. torque 는 N·m, angular_velocity 는 rad/s 이다. rpm 을 그대로 넣으면 틀리므로 ω = 2π·rpm/60 으로 먼저 환산해야 한다. 두 값의 부호는 그대로 곱해진다. 유한한 Decimal 문자열만 허용하며 호출자의 Decimal 설정과 독립적으로 50자리 유효숫자 HALF_EVEN으로 계산한다. 계산 범위 초과는 입력 오류다.

Input Schema

NameRequiredDescriptionDefault
torqueYes
angular_velocityYes

Output Schema

NameRequiredDescriptionDefault
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
powerYes
traceYes계산 근거(tool, formula, inputs, steps, output)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent, yet the description still adds real value: input must be finite Decimal strings, computation uses 50 significant digits HALF_EVEN independent of the caller's Decimal context, and out-of-range computation is treated as an input error. These are non-obvious behavioral traits an agent cannot infer otherwise.

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?

Five short sentences, formula and units front-loaded, then the rpm pitfall, then precision/range behavior. No filler; every sentence conveys a constraint the caller needs.

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

Completeness5/5

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

Output schema exists, so return values need not be described. With two parameters fully explained (units, format), precision behavior stated, and range errors defined, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 carry the load, and it does: torque is N·m, angular_velocity is rad/s, both must be finite Decimal strings, and the rpm pitfall is flagged. It stops short of giving format examples, but the unit and type semantics are fully supplied.

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?

States a specific verb and resource ('회전 일률 P = τ·ω 계산') plus the output unit (W), and the formula itself distinguishes it from neighboring power tools such as engineering.electrical_power or engineering.pump_hydraulic_power. No ambiguity about what the tool computes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete call-time guidance: rpm must be converted with ω = 2π·rpm/60 first, since passing rpm directly is wrong, and sign propagation is explained. It does not route the agent to or away from sibling tools, but for a single-formula calculator the invocation guidance is the relevant part.

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

Deploy Server

Other Tools