Arc Flash Platform — Estudos Elétricos

Partida de motor: afundamento de tensão

partida_motor

Read-only

Afundamento de tensão na partida de motor por divisor fasorial fonte→cabo→motor (C ∝ V²). fonte_tipo ∈ {scc (nível de curto scc_MVA), trafo (fonte_trafo_kVA+fonte_trafo_Vcc_pct, com rede a montante opcional fonte_scc_montante_MVA), gerador (fonte_gmg_kVA+fonte_gmg_xd_pct, X'd transitório)}. Trafo dedicado e GMG são os casos SEVEROS de afundamento. metodo ∈ {direta, estrela_triangulo, compensadora_65, compensadora_80, soft_starter, vfd} (aceita 'compensadora'→tap 80% e 'soft'→soft_starter). fp_partida = FP de rotor bloqueado; Cp_Cn = conjugado de partida/nominal; C_load_pu = conjugado da carga (×Cn); SEM ele a aceleração NÃO é avaliada. Gratuito (uso limitado).

Input Schema

Name	Required	Default
`fp`	No
`eta`	No
`In_A`	No
`Cp_Cn`	No
`Ip_In`	No
`cabo_m`	No
`metodo`	No	direta
`api_key`	No
`scc_MVA`	No
`cabo_mm2`	No
`tensao_V`	Yes
`C_load_pu`	No
`fonte_tipo`	No	scc
`fp_partida`	No
`potencia_kW`	Yes
`dv_limite_pct`	No
`fonte_gmg_kVA`	No
`fonte_trafo_kVA`	No
`fonte_gmg_xd_pct`	No
`fonte_trafo_Vcc_pct`	No
`fonte_scc_montante_MVA`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedJul 3, 2026

addedInput schema / properties / fonte_gmg_kVA

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

addedInput schema / properties / fonte_gmg_xd_pct

Added value: +{
+  "default": 25,
+  "title": "Fonte Gmg Xd Pct",
+  "type": "number"
+}

addedInput schema / properties / fonte_scc_montante_MVA

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

addedInput schema / properties / fonte_tipo

Added value: +{
+  "default": "scc",
+  "title": "Fonte Tipo",
+  "type": "string"
+}

addedInput schema / properties / fonte_trafo_Vcc_pct

Added value: +{
+  "default": 5,
+  "title": "Fonte Trafo Vcc Pct",
+  "type": "number"
+}

addedInput schema / properties / fonte_trafo_kVA

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

addedInput schema / properties / scc_MVA / anyOf

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

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

changedInput schema / required

Previous value: -[
-  "potencia_kW",
-  "tensao_V",
-  "scc_MVA"
-]New value: +[
+  "potencia_kW",
+  "tensao_V"
+]

Changed5 schema fields changedJul 2, 2026

addedInput schema / properties / C_load_pu

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

addedInput schema / properties / Cp_Cn

Added value: +{
+  "default": 2,
+  "title": "Cp Cn",
+  "type": "number"
+}

addedInput schema / properties / In_A

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

addedInput schema / properties / dv_limite_pct

Added value: +{
+  "default": 10,
+  "title": "Dv Limite Pct",
+  "type": "number"
+}

addedInput schema / properties / fp_partida

Added value: +{
+  "default": 0.25,
+  "title": "Fp Partida",
+  "type": "number"
+}

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 only declare readOnlyHint=true, and the description adds real behavioral context: conditional parameter requirements per fonte_tipo, the severity of dedicated transformer/GMG sources, the acceleration-gating role of C_load_pu, and the 'Gratuito (uso limitado)' licensing/usage limit. It does not describe the response, but that is a minor omission for a read-only calculator.

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 core model is front-loaded, and every clause is information-dense—enum expansions are necessary because the schema has no descriptions. It is a dense block rather than clearly sectioned prose, but there is little wasted text.

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 21-parameter, no-output-schema tool, the description covers the most complex parameter families well but omits several input meanings (cable, current, voltage-limit) and says nothing about the result. Adequate for the source/method mechanics, incomplete overall.

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 carries the full burden. It does well on the hard cases—fonte_tipo's three modes and their associated fields (scc_MVA, trafo kVA/Vcc, gmg kVA/X'd), the six metodo values with aliases, fp_partida, Cp_Cn and C_load_pu—but leaves fp, eta, In_A, Ip_In, cabo_m, cabo_mm2 and dv_limite_pct undocumented, which are non-obvious and matter for the calculation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific physical calculation: voltage dip at motor start via a source→cable→motor phasor divider with C ∝ V². It is clearly more than a restatement of the name, though it never explicitly distinguishes itself from the adjacent sibling tempo_partida_motor or dimensionar_cabo.

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?

It explains which inputs belong to each fonte_tipo mode and flags dedicated transformer and GMG as the severe cases, plus the condition that acceleration is not evaluated without C_load_pu. However, it gives no explicit when-to-use-this-vs-an-alternative routing, e.g. against tempo_partida_motor, so usage is only implied.

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?