Skip to main content
Glama

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
NameRequiredDescriptionDefault
fpNo
etaNo
In_ANo
Cp_CnNo
Ip_InNo
cabo_mNo
metodoNodireta
api_keyNo
scc_MVANo
cabo_mm2No
tensao_VYes
C_load_puNo
fonte_tipoNoscc
fp_partidaNo
potencia_kWYes
dv_limite_pctNo
fonte_gmg_kVANo
fonte_trafo_kVANo
fonte_gmg_xd_pctNo
fonte_trafo_Vcc_pctNo
fonte_scc_montante_MVANo

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true; the description adds behavioral details (source types, method, parameter interdependencies) but does not describe the output or confirm read-only behavior. The 'free limited use' note is extraneous.

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 a single dense paragraph that front-loads the purpose. Each sentence adds value, though it could be better structured with bullet points for parameter sets.

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 21 parameters and no output schema, the description is incomplete. It lacks explanation for many parameters, does not specify the output format (e.g., voltage dip percentage), and omits usage conditions like required prerequisites or result interpretation.

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?

With schema description coverage at 0%, the description adds meaning for about 6 key parameters (fonte_tipo, metodo, fp_partida, Cp_Cn, C_load_pu) but leaves many others (tensao_V, potencia_kW, cabo_m, etc.) unexplained. It partially compensates but is insufficient for 21 parameters.

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 the tool calculates voltage dip during motor starting using a phasor divider model. It specifies the main verb (calculates voltage dip) and resource (motor starting), distinguishing it from sibling tools like tempo_partida_motor (motor 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 Guidelines4/5

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

The description provides context on when to use different source types (e.g., dedicated transformer and generator are severe cases) and notes that acceleration evaluation requires C_load_pu. However, it does not explicitly state when not to use the tool or compare with alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct electrical calculation or administrative task. Overlapping concepts like 'calcular_curto_circuito' and 'partida_motor' have clearly different purposes (short-circuit vs. voltage dip). No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in Portuguese, using snake_case. Examples include 'calcular_curto_circuito', 'dimensionar_cabo', and 'verificar_seccionamento'. There are no deviations or mixed conventions.

Tool Count5/5

20 tools is well-scoped for a specialized electrical engineering calculations server. Each tool addresses a specific need without redundancy or excessive breadth. The count feels appropriate for the domain.

Completeness5/5

The tool set covers a comprehensive lifecycle: calculation (short-circuit, arc flash, motor starting), design (cable sizing, CT sizing, capacitor banks), coordination (protection time curves), verification (shock protection), and workflow (report generation, quote request). No obvious gaps for the intended purpose.

Resources