Arc Flash Platform — Estudos Elétricos

Dimensionamento de TC (IEC 61869-2)

dimensionar_tc

Read-only

Dimensiona o TC de proteção (IEC 61869-2 / NBR 6856): menor primário comercial que NÃO satura na falta, considerando o burden REAL (relé+fiação) e o ALF efetivo. xr (X/R) = liga o critério de saturação na falta ASSIMÉTRICA (offset CC, IEEE C37.110): um TC que passa no simétrico pode saturar no transitório, atrasar o relé e ELEVAR a energia incidente de arco. I_load_A+Fter = corrente de carga p/ o critério térmico contínuo. Ith_A/Idyn_A = corrente térmica (I²t, com t_curto_s/tth_s) e dinâmica de catálogo → robustez à falta passante (se o TC AGUENTA o curto sem dano térmico/mecânico). Rct_ohm = R do secundário de catálogo, do enrolamento EM USO (None → estimada, e a resposta diz que estimou e por qual fórmula). AVALIAR O TC INSTALADO: primario_A avalia só aquela relação (em vez de procurar a menor que atende) e devolve tensão de saturação, ALF efetivo, ALF exigido no simétrico e com a componente CC, margem, Ks, tempo até a saturação e o resultado. TC multi-relação: primario_A = a derivação em uso e primario_pleno_A = a relação de placa — a classe vale para o enrolamento inteiro. CLASSE: ALF + burden_VA (IEC, ex.: 10P20 de 25 VA) OU classe_abnt na notação antiga da ABNT (ex.: '10B200', '2,5B100'; o tipo A, de alta reatância, é recusado). SIMULAÇÃO NO TEMPO (só com primario_A, exige xr): pickup_sec_A = pickup do elemento no secundário [A] liga a simulação da calculadora de saturação do IEEE PSRC e devolve o instante em que o fluxo alcança o de saturação, a menor razão entre a fundamental que o relé vê e a ideal e o atraso até o pickup. remanencia_pct = remanência inicial em % do fluxo de saturação (padrão 0; a classe PR garante até 10 %; 40 % quando desconhecida, pelo manual do RET630 da ABB). Gratuito (uso limitado).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`xr`	No
`ALF`	No
`Fter`	No
`Icc_A`	Yes
`Ith_A`	No
`tth_s`	No
`Idyn_A`	No
`Rct_ohm`	No
`api_key`	No
`I_load_A`	No
`burden_VA`	No
`cable_ohm`	Yes
`relay_ohm`	Yes
`t_curto_s`	No
`primario_A`	No
`classe_abnt`	No
`pickup_sec_A`	No
`secundario_A`	Yes
`remanencia_pct`	No
`primario_pleno_A`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

addedInput schema / properties / pickup_sec_A

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Pickup Sec A"
+}

addedInput schema / properties / remanencia_pct

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

Changed10 schema fields changedOct 4, 2026

addedInput schema / properties / ALF / anyOf

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

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

addedInput schema / properties / burden_VA / anyOf

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

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

addedInput schema / properties / classe_abnt

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Classe Abnt"
+}

addedInput schema / properties / primario_A

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

addedInput schema / properties / primario_pleno_A

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Primario Pleno A"
+}

changedInput schema / required

Previous value: -[
-  "Icc_A",
-  "secundario_A",
-  "ALF",
-  "burden_VA",
-  "relay_ohm",
-  "cable_ohm"
-]New value: +[
+  "Icc_A",
+  "secundario_A",
+  "relay_ohm",
+  "cable_ohm"
+]

Changed4 schema fields changedJul 3, 2026

addedInput schema / properties / Idyn_A

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

addedInput schema / properties / Ith_A

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

addedInput schema / properties / t_curto_s

Added value: +{
+  "default": 1,
+  "title": "T Curto S",
+  "type": "number"
+}

addedInput schema / properties / tth_s

Added value: +{
+  "default": 1,
+  "title": "Tth S",
+  "type": "number"
+}

Changed4 schema fields changedJul 2, 2026

addedInput schema / properties / Fter

Added value: +{
+  "default": 1,
+  "title": "Fter",
+  "type": "number"
+}

addedInput schema / properties / I_load_A

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "I Load A"
+}

addedInput schema / properties / Rct_ohm

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

addedInput schema / properties / xr

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

First observedJun 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only cover readOnlyHint, so the description carries the behavioral load and does it well: it discloses the rate limit ('Gratuito (uso limitado)'), the silent-estimation behavior for Rct_ohm ('None → estimada, e a resposta diz que estimou e por qual fórmula'), and the defaulting semantics for remanencia_pct. It also enumerates what the response returns (saturação, ALF efetivo, margem, Ks, tempo até saturação).

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?

It is dense and long, but front-loaded (purpose first, then optional criteria, then modes), and nearly every clause conveys a distinct engineering rule or parameter behavior. It could be broken into labelled sections rather than a single block of prose, which is the main structural weakness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 20-parameter engineering tool with no output schema, the description supplies the criteria, the mode switches and the returned quantities, so an agent has enough to call it correctly. It does not, however, cover every required parameter's meaning or state the units/bounds expected for the electrical inputs.

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%, so the description must compensate, and it does for the high-value parameters: xr, I_load_A+Fter, Ith_A/Idyn_A, t_curto_s/tth_s, Rct_ohm, primario_A, primario_pleno_A, ALF/burden_VA, classe_abnt, pickup_sec_A, remanencia_pct, and even api_key by implication. Gaps remain for Icc_A, secundario_A, relay_ohm and cable_ohm, but overall it adds substantial meaning beyond the bare schema.

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 and resource ('Dimensiona o TC de proteção') plus the governing standards (IEC 61869-2 / NBR 6856), and immediately narrows scope with 'menor primário comercial que NÃO satura na falta'. No sibling is named, but the domain is so specific that it cannot be confused with calcular_curto_circuito, dimensionar_cabo, or the other sizing tools.

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

Usage Guidelines3/5

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

Usage is implied through the parameter-driven modes ('AVALIAR O TC INSTALADO: primario_A avalia só aquela relação... em vez de procurar a menor que atende', 'SIMULAÇÃO NO TEMPO (só com primario_A, exige xr)'), which tells the agent which mode a given call enters. However there is no explicit statement of when to choose this tool over sibling tools, nor any exclusion criteria beyond the ABNT type-A refusal.

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?