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

TableJSON 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 indicate readOnlyHint=true. The description adds valuable behavioral context: it computes voltage sag, requires certain parameters for acceleration evaluation, and notes that dedicated transformer/generator are severe cases. It also mentions limited free usage. 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph. It is front-loaded with the purpose but packs many details in a somewhat hard-to-parse structure. It could be improved with bullet points or clearer separation for each parameter group.

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

Completeness2/5

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

Given the tool's complexity (21 parameters, no output schema, 0% schema description coverage), the description does not fully compensate. It lacks explanations for many parameters, does not describe the return value or result structure, and does not provide comprehensive usage guidelines for all input combinations.

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 (fonte_tipo variants, metodo options, fp_partida, Cp_Cn, C_load_pu) but does not cover all 21 parameters, especially required ones like potencia_kW and tensao_V. This partial coverage is adequate but not complete.

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 voltage sag during motor start using a phasor divider. The title and first sentence specify the exact resource and action, distinguishing it from sibling tools like 'tempo_partida_motor' which likely computes start time.

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?

The description provides some usage context: source types and their severity, the need for C_load_pu to evaluate acceleration, and method aliases. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or when not to use it.

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?