Skip to main content
Glama

Arc Flash Platform — Estudos Elétricos

Tempo de partida de motor (curva T×n + rotor térmico)

tempo_partida_motor
Read-only

Simula a partida DIRETA no tempo (RK4, J·dω/dt = T_motor − T_carga): tempo de aceleração, se o motor PARTE ou trava, e o térmico de rotor bloqueado (I²t da partida vs tempo de rotor bloqueado de placa, critério Petrobras N-313). polos = nº de polos; inercia_kgm2 = J total (motor+carga); tipo_carga ∈ {constante, linear, parabolica (bomba/ventilador)}; conjugado_partida_carga_pu /conjugado_pleno_pu = conjugado da carga (×Cn do motor) em n=0 e a plena rotação; t_rotor_bloqueado_s liga o veredito térmico. Gratuito.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fpNo
etaNo
Cp_CnNo
Ip_InNo
polosYes
cabo_mNo
api_keyNo
scc_MVAYes
cabo_mm2No
tensao_VYes
fp_partidaNo
tipo_cargaNoparabolica
potencia_kWYes
inercia_kgm2Yes
conjugado_pleno_puNo
t_rotor_bloqueado_sNo
conjugado_partida_carga_puNo

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, consistent with the simulation. The description adds valuable behavioral details: the numerical method (RK4, differential equation), the specific standard (Petrobras N-313), and the evaluated criteria (I²t vs locked-rotor time). This exceeds minimum disclosure without contradicting annotations.

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, information-dense paragraph with no wasted words. It front-loads the purpose and method. However, it could be more structured (e.g., bullet points for parameters) to improve readability.

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?

Given the complexity (17 parameters, no output schema), the description explains the simulation method and some outputs (acceleration time, start/stall, thermal verdict) but omits many parameter meanings and does not describe the full response format. Behavior on invalid inputs or data limits is not addressed, leaving gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 5 of 17 parameters (polos, inercia_kgm2, tipo_carga, conjugado_partida_carga_pu, conjugado_pleno_pu, t_rotor_bloqueado_s) but leaves critical parameters like potencia_kW, tensao_V, and scc_MVA unexplained. The value added is partial.

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 specifies a precise action: simulating direct motor starting in time using RK4, including acceleration time, start/stall determination, and thermal rotor blocked verification per the Petrobras N-313 criterion. It clearly distinguishes from sibling tools like 'partida_motor' by emphasizing the 'DIRETA' method and thermal analysis.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool over alternatives such as 'partida_motor'. No prerequisites, context, or exclusions are mentioned, leaving the agent to infer usage from the purpose alone.

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