Arc Flash Platform — Estudos Elétricos

Dessintonia de banco de capacitores (reator anti-ressonância)

dessintonia_capacitor

Read-only

Banco dessintonizado (reator série anti-ressonância). Informe p_pct (fator de dessintonia XL/XC, ex.: 7 ou 14) OU L_mH. Devolve a tensão ELEVADA no capacitor V/(1−p), a corrente pelo reator, o reativo efetivo Q/(1−p), a frequência de sintonia e a classe de tensão sugerida do capacitor (IEC 60831). Com scc_MVA, avalia a ressonância paralela com a rede. Gratuito.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`L_mH`	No
`p_pct`	No
`Q_kvar`	Yes
`api_key`	No
`scc_MVA`	No
`Un_cap_kV`	No
`tensao_kV`	Yes

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, confirming no side effects. The description adds behavioral details such as raised voltage calculation and optional resonance evaluation, improving transparency beyond annotations.

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?

Description is concise and front-loaded with purpose. Some technical formulas and references are included but not excessive. Could be slightly more compact without losing value.

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?

Outputs are listed, and optional resonance evaluation is noted. However, the optional parameter Un_cap_kV's effect is not explained, and error conditions are missing. Adequate but not comprehensive.

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

Parameters2/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. Only two parameters (p_pct, L_mH) are explained, while required parameters Q_kvar and tensao_kV are not described, leaving gaps.

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 the tool calculates detuned capacitor bank parameters, specifying the inputs and outputs. It distinguishes itself from sibling tools by focusing on a specific calculation (anti-resonance reactor), with no ambiguity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'corrigir_fator_potencia' or other calculators. The description only explains parameters, not usage context or exclusions.

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

All Arc Flash Platform — Estudos Elétricos tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool targets a specific calculation or parameter (e.g., short-circuit, incident energy, cable sizing). Even related tools like partida_motor (voltage dip) and tempo_partida_motor (acceleration time) have distinct purposes. Descriptions clearly differentiate them.

Naming Consistency5/5

All tool names use snake_case and predominantly follow a verb_noun pattern (calcular_, corrigir_, dimensionar_). The few deviations like dano_transformador or k_factor_transformador are still clear and do not break overall consistency.

Tool Count5/5

With 20 tools, the server covers a wide range of electrical engineering calculations without being bloated. Each tool serves a specific purpose, and the count feels well-scoped for the domain.

Completeness4/5

The tool set covers short-circuit, arc flash, protection coordination, cable sizing, and other key areas. Missing advanced topics like load flow are outside the stated scope; only minor gaps like direct relay coordination tools are absent.

Resources

Need Help?