Arc Flash Platform — Estudos Elétricos

Correção de fator de potência (REN 1.000)

corrigir_fator_potencia

Read-only

Dimensiona o banco de capacitores para corrigir o fator de potência à meta (REN ANEEL nº 1.000; FP-alvo padrão 0,92). Com tensao_kV também dá a corrente nominal do banco e a norma (IEC 60831/60871). Un_cap_kV = tensão de placa do capacitor: se ele opera abaixo da Un, entrega MENOS kvar (derating Q∝V²) e a correção real cai — informe p/ não superestimar. carga_min_pct = carregamento mínimo (%): dispara o alerta de SOBRECORREÇÃO capacitiva (banco fixo em carga leve → FP capacitivo, faturável). scc_MVA = curto na barra do banco → inrush de manobra e a corrente de PROJETO da proteção/cabo do banco (1,5·In BT, IEEE C37.012). Gratuito.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No
`fp_meta`	No
`scc_MVA`	No
`fp_atual`	Yes
`Un_cap_kV`	No
`tensao_kV`	No
`potencia_kW`	Yes
`carga_min_pct`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 3, 2026

addedInput schema / properties / scc_MVA

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Scc Mva"
+}

Changed2 schema fields changedJul 2, 2026

addedInput schema / properties / Un_cap_kV

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Un Cap Kv"
+}

addedInput schema / properties / carga_min_pct

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Carga Min Pct"
+}

First observedJun 30, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations provide readOnlyHint=true, confirming no side effects. The description adds value by disclosing derating behavior (Q∝V²), overcorrection alerts, and inrush current calculations, which are beyond the annotation.

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?

The description is well-structured with a clear purpose sentence followed by parameter-specific notes. It is somewhat long but each sentence adds unique value; no redundancy.

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?

No output schema exists. The description mentions outputs (current, standard, alerts, inrush current) but doesn't define the return format or what is definitely provided. For a calculation tool, output specification is important.

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 coverage is 0%, but the description explains optional parameters (tensao_kV, Un_cap_kV, carga_min_pct, scc_MVA) in detail. However, required parameters (potencia_kW, fp_atual) are only implied by the overall purpose, not explicitly described.

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 explicitly states the tool's purpose: dimensioning capacitor banks for power factor correction per REN 1.000 with a target PF of 0.92. It distinguishes itself from sibling tools like 'dessintonia_capacitor' by focusing on correction sizing.

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 explicit guidance on when to use this tool versus alternatives (e.g., 'dessintonia_capacitor' or other calc tools). The description lacks 'use this when...' or 'instead of...' statements.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?