k_factor_transformadorK-factor (UL 1561) a partir do espectro de corrente {ordem: % de I1}, ex.: {"3": 70, "5": 45, "7": 30}. Devolve o K-factor, o K-rating comercial (trafo K-rated para cargas não-lineares), o F_HL (derating de perdas parasitas, IEEE C57.110) e o THD de corrente. Gratuito.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | ||
| espectro_harmonico | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, consistent with a non-destructive calculation. The description adds that the tool returns multiple computed values and is free, but does not detail rate limits or other constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no wasted words. It front-loads the purpose and includes a concrete example efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description's enumeration of outputs (K-factor, K-rating, F_HL, THD) is valuable. It covers input format and output, but could add details on error handling or value ranges.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description bears the burden. It explains the main parameter 'espectro_harmonico' with an example format. However, it does not mention the optional 'api_key' parameter, leaving its purpose unclear.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool calculates K-factor, K-rating, F_HL, and THD from a harmonic current spectrum, referencing standards UL 1561 and IEEE C57.110. It distinguishes itself from sibling tools (e.g., 'calcular_curto_circuito') by its specific purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides an example input format and lists outputs, implying use for transformer K-factor calculation. It does not explicitly state when not to use it or name alternatives, but the sibling list provides context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct electrical calculation or administrative task. Overlapping concepts like 'calcular_curto_circuito' and 'partida_motor' have clearly different purposes (short-circuit vs. voltage dip). No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern in Portuguese, using snake_case. Examples include 'calcular_curto_circuito', 'dimensionar_cabo', and 'verificar_seccionamento'. There are no deviations or mixed conventions.
20 tools is well-scoped for a specialized electrical engineering calculations server. Each tool addresses a specific need without redundancy or excessive breadth. The count feels appropriate for the domain.
The tool set covers a comprehensive lifecycle: calculation (short-circuit, arc flash, motor starting), design (cable sizing, CT sizing, capacitor banks), coordination (protection time curves), verification (shock protection), and workflow (report generation, quote request). No obvious gaps for the intended purpose.