SooTool

engineering.electrical_power

Read-onlyIdempotent

Calculates all four DC circuit values (power, voltage, current, resistance) from any two known Decimal inputs using P=VI=I²R=V²/R and returns the complete set.

Instructions

직류 전력 방정식 P=VI=I²R=V²/R에서 나머지 값을 구한다. power(W), voltage(V), current(A), resistance(Ω) 중 정확히 2개를 Decimal 문자열로 넣으면 네 값을 모두 돌려준다. (P,R) 조합은 제곱근을 쓰며 양의 근만 반환한다. 오용 주의: 교류의 유효전력은 역률을 곱해야 하므로 three_phase_power 등을 쓴다.

Input Schema

Name	Required	Description	Default
`power`	No
`current`	No
`voltage`	No
`resistance`	No

Output Schema

Name	Required	Description
`_meta`	No	서버가 붙이는 영수증(integrity), 엔진, 힌트
`power`	Yes
`trace`	Yes	계산 근거(tool, formula, inputs, steps, output)
`current`	Yes
`voltage`	Yes
`resistance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 29, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations declare readOnly/idempotent, and the description adds value beyond them: it notes (P,R) requires a square root and returns only the positive root, and that all four values are returned. This is meaningful behavioral context not in the annotations.

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?

Front-loaded formula and input rule, followed by the square-root nuance and the AC misuse warning. Three dense sentences with no filler.

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?

For a 4-param tool with an output schema and 0% schema coverage, the description supplies the input constraint, units, format, root behavior, and sibling routing. Nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate; it names all four parameters (power W, voltage V, current A, resistance Ω), specifies the exact-2 input rule, and mandates Decimal strings. This fully documents parameter meaning and format.

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 (solves DC power equation P=VI=I²R=V²/R for the remaining values) and clearly distinguishes itself from the AC-oriented sibling three_phase_power. An agent can identify the tool's job without inspecting 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 Guidelines5/5

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

Explicitly says to supply exactly 2 of the 4 quantities and warns against misuse for AC real power, directing to three_phase_power instead. When-to-use and when-not-to-use are both covered.

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

Deploy Server