Arc Flash Platform — Estudos Elétricos

Curto-circuito (IEC 60909)

calcular_curto_circuito

Read-only

Curto-circuito (IEC 60909) pelo algoritmo da plataforma: Icc 3φ/2φ/fase-terra, X/R e pico. Informe a rede por potencia_curto_mva OU icc_rede_kA. com_transformador=True dá o Icc no secundário (trafo_*). xr_rede/xr_trafo = relações X/R (regem κ, pico ip e assimetria, isto é, o making do disjuntor); tipo_aterramento ∈ {solido, resistivo, isolado} + Rn_ohm regem a corrente de falta fase-terra (Icc_1φ). com_cabo=True (+ cabo_secao_mm2/cabo_m) dá o Icc no PONTO de instalação após o cabo (menor que no barramento). fator_c (nulo = a Tabela 1 da IEC 60909) e aplicar_kt (True = K_T do §6.3.3) são a BASE: fator_c 1,0 com aplicar_kt=False reproduz um estudo feito em tensão nominal, FORA do §7.1.2, e a resposta avisa. Gerador como fonte em BT: use xr_rede ≈ 6,7 (X″d/R_Gf, §6.6.1), não 10 ou 20. Gratuito (uso limitado).

Input Schema

Name	Required	Default
`Rn_ohm`	No
`cabo_m`	No
`api_key`	No
`fator_c`	No
`xr_rede`	No
`com_cabo`	No
`xr_trafo`	No
`tensao_kv`	Yes
`trafo_kVA`	No
`aplicar_kt`	No
`icc_rede_kA`	No
`trafo_V2_kv`	No
`cabo_material`	No	Cu
`trafo_Vcc_pct`	No
`cabo_secao_mm2`	No
`tipo_aterramento`	No	solido
`com_transformador`	No
`potencia_curto_mva`	No
`cabo_num_condutores`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

addedInput schema / properties / aplicar_kt

Added value: +{
+  "default": true,
+  "title": "Aplicar Kt",
+  "type": "boolean"
+}

addedInput schema / properties / fator_c

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

Changed5 schema fields changedJul 3, 2026

addedInput schema / properties / cabo_m

Added value: +{
+  "default": 50,
+  "title": "Cabo M",
+  "type": "number"
+}

addedInput schema / properties / cabo_material

Added value: +{
+  "default": "Cu",
+  "title": "Cabo Material",
+  "type": "string"
+}

addedInput schema / properties / cabo_num_condutores

Added value: +{
+  "default": 1,
+  "title": "Cabo Num Condutores",
+  "type": "integer"
+}

addedInput schema / properties / cabo_secao_mm2

Added value: +{
+  "default": 50,
+  "title": "Cabo Secao Mm2",
+  "type": "number"
+}

addedInput schema / properties / com_cabo

Added value: +{
+  "default": false,
+  "title": "Com Cabo",
+  "type": "boolean"
+}

Changed9 schema fields changedJul 2, 2026

addedInput schema / properties / Rn_ohm

Added value: +{
+  "default": 0,
+  "title": "Rn Ohm",
+  "type": "number"
+}

addedInput schema / properties / icc_rede_kA

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Icc Rede Ka"
+}

addedInput schema / properties / potencia_curto_mva / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / potencia_curto_mva / default
```
Added value: +null
```
removedInput schema / properties / potencia_curto_mva / type
```
Removed value: -"number"
```

addedInput schema / properties / tipo_aterramento

Added value: +{
+  "default": "solido",
+  "title": "Tipo Aterramento",
+  "type": "string"
+}

addedInput schema / properties / xr_rede

Added value: +{
+  "default": 10,
+  "title": "Xr Rede",
+  "type": "number"
+}

addedInput schema / properties / xr_trafo

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

changedInput schema / required

Previous value: -[
-  "tensao_kv",
-  "potencia_curto_mva"
-]New value: +[
+  "tensao_kv"
+]

First observedJun 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Read-only annotations already cover the safety profile, and the description adds real behavioral context beyond them: the response warns when fator_c=1.0 with aplicar_kt=False is used outside §7.1.2, and it discloses 'Gratuito (uso limitado)'. It does not describe the result payload shape, but the warnings and the metering note are non-trivial disclosures.

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?

Dense and front-loaded: purpose first, then the input-selection rules, then the accuracy caveat. Some IEC section citations (§6.3.3, §6.6.1, §7.1.2) add authority but also weight; the text is long, though nearly every clause carries decision-relevant information.

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?

For a 19-parameter, no-output-schema tool the description covers the critical input logic but leaves several defaulted parameters (transformer kVA/voltage/impedance, cable material, conductor count) undescribed, so an agent cannot confidently change them. Adequate, but with a clear gap given the schema's zero description coverage.

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 coverage is 0% across 19 parameters, so the description carries the full burden and does well: it explains the mutually exclusive network inputs, the trafo_* group, xr_rede/xr_trafo's physical role (κ, peak ip, asymmetry, breaker making), the aterramento/Rn_ohm pair driving Icc_1φ, and the fator_c/aplicar_kt base. trafo_kVA, trafo_V2_kv, trafo_Vcc_pct, cabo_material and cabo_num_condutores are only implied by 'trafo_*'/'cabo_*' and never given units or meaning.

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+resource with scope: short-circuit calculation per IEC 60909 producing Icc 3φ/2φ/phase-earth, X/R and peak. The output set is listed up front, which cleanly separates it from siblings such as calcular_energia_incidente or dimensionar_cabo without needing their schemas.

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 explicit alternatives for the network source ('potencia_curto_mva OU icc_rede_kA') and conditional guidance for branches (com_transformador=True, com_cabo=True, generator source → xr_rede≈6,7). It never states when to prefer this tool over a sibling (e.g. when peak current rather than incident energy is wanted), so no explicit exclusion is present.

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?