Arc Flash Platform — Estudos Elétricos

Curto-circuito (IEC 60909)

calcular_curto_circuito

Read-only

Curto-circuito (IEC 60909) pelo motor 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 — 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). Gratuito (uso limitado).

Input Schema

TableJSON Schema

Name	Required	Default
`Rn_ohm`	No
`cabo_m`	No
`api_key`	No
`xr_rede`	No
`com_cabo`	No
`xr_trafo`	No
`tensao_kv`	Yes
`trafo_kVA`	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.

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/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, which aligns with the calculation nature. The description adds behavioral details: 'Gratuito (uso limitado)' indicates usage limits, and explains how parameters affect results (e.g., com_cabo gives fault current at installation point, lower than busbar). No contradictions with 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?

The description is compact and front-loaded with the core purpose. It uses abbreviations and compact notation (e.g., 'Icc 3φ/2φ/fase-terra') to save space. While it is a single dense paragraph, it efficiently conveys information without excessive verbosity. Minor structural improvement (e.g., bullet points) could enhance readability.

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?

Given the high complexity (17 parameters, no output schema), the description provides substantial context but does not explain all parameters nor describe the output format (e.g., what fields are returned). With readOnlyHint, safety is assured, but an agent would still need to infer output structure. Missing details on unmentioned parameters reduce completeness somewhat.

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 description coverage is 0%, so the description must compensate. It explains several key parameters (potencia_curto_mva, icc_rede_kA, xr_rede, xr_trafo, tipo_aterramento, Rn_ohm, com_cabo, cabo_secao_mm2, cabo_m) with functional meanings. However, it omits explanations for tensao_kv, trafo_kVA, trafo_V2_kv, trafo_Vcc_pct, cabo_material, cabo_num_condutores, and api_key, which are not described. Thus it partially compensates.

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 it calculates short-circuit currents per IEC 60909, specifying fault types (3φ, 2φ, phase-ground), X/R, and peak current. It uses specific verbs and resource names, and the title reinforces the standard. This distinguishes it from sibling tools like calcular_energia_incidente or grupo_gerador.

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?

The description provides clear guidance on key parameter choices (e.g., use potencia_curto_mva OR icc_rede_kA for network data; com_transformador for secondary side; com_cabo for cable effects; tipo_aterramento for phase-ground fault). It does not explicitly state when not to use the tool versus siblings, but the context is adequate for an agent to decide.

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?