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, porque 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

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

Behavior5/5

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

With readOnlyHint=true already covering the safety profile, the description goes far beyond annotations: it explains the asymmetric-fault saturation criterion, the real burden basis, what happens when Rct_ohm is None (estimation plus disclosure of the formula), and precisely what the IEEE PSRC simulation returns (instant of saturation, minimum fundamental ratio, pickup delay). It even discloses the free/limited-use constraint – rich behavioral context.

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?

Front-loaded with the core purpose, then organized by parameter families and by operating mode. Given 20 parameters and zero schema descriptions, the length is justified and no sentence is filler. Readability is dented by dense jargon and a single unbroken block, but nothing is wasted.

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?

There is no output schema, and the description compensates by naming what the evaluation mode returns (tensão de saturação, ALF efetivo, margem, Ks, tempo até saturação) and what the time simulation returns. The main omission is authentication/api_key behavior and a fuller definition of the four required electrical inputs, but overall an agent could call this correctly.

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 description coverage is 0% across 20 parameters, so the description must carry the load, and it mostly does: 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 and remanencia_pct all get meaning and units. Gaps remain for required parameters such as secundario_A, Icc_A, relay_ohm and cable_ohm (only indirectly implied by 'burden REAL (relé+fiação)'), and api_key is never mentioned.

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?

Opens with a precise verb+resource: 'Dimensiona o TC de proteção (IEC 61869-2 / NBR 6856)'. It states the exact engineering objective (menor primário comercial que não satura na falta) and leaves no ambiguity about what the tool returns. No sibling tool covers CT sizing, so differentiation is implicit but the scope is unmistakable.

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 clear mode selection rules: 'AVALIAR O TC INSTALADO' when primario_A is supplied, versus searching for the smallest adequate ratio otherwise; and simulation mode requires primario_A plus xr. It also states the class can be given either as ALF+burden_VA or classe_abnt. It never names a sibling alternative, which is the only missing piece.

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?