Skip to main content
Glama

Arc Flash Platform — Estudos Elétricos

Curva de dano de transformador (IEEE C57.109)

dano_transformador
Read-only

Curva de dano a faltas passantes do transformador (IEEE C57.109/C57.12.59): categoria, corrente de falta passante máxima (In/Z), ponto ANSI e ponto de inrush — para coordenar a proteção a montante. fases ∈ {3ph,1ph}; frequencia_falta ∈ {infrequent,frequent}; tipo ∈ {liquid,dry}; t_inrush_ms = patamar de tempo do ponto de inrush. ligacao (IEEE C37.91) refere a curva ao OUTRO lado para coordenar com a proteção de lá: {dyg,ygd} Δ-Yg ×0,58 · {dd,yy} ×0,87 · {ygyg,none} ×1,0. Gratuito (uso limitado).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipoNoliquid
Vn_kVYes
fasesNo3ph
Sn_kVAYes
Vcc_pctYes
api_keyNo
ligacaoNonone
k_inrushNo
t_inrush_msNo
frequencia_faltaNoinfrequent

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating no side effects. The description adds that it is free with limited use but does not elaborate on authentication, rate limits, or output behavior. With annotations covering safety, the added value is modest.

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 paragraph, front-loading the core purpose. It is reasonably concise but could be better structured with bullet points or separate sections for parameter details.

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?

Despite complexity (10 parameters, no output schema), the description omits the expected return format (the curve data?) and does not explain the three required parameters. It feels incomplete for an AI agent to use correctly without additional knowledge.

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 explain parameters. It adds meaning for optional params like ligacao (multiplier explanation) and t_inrush_ms (inrush point time), but fails to explain required parameters Sn_kVA, Vn_kV, Vcc_pct. This is a significant gap.

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 generates a transformer damage curve per IEEE C57.109, with specific parameters and purpose for coordinating upstream protection. It distinguishes from sibling tools like calcular_curto_circuito which handles short-circuit calculations.

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 mentions the tool is for coordinating upstream protection, but does not explicitly state when to use this tool versus alternatives like tempo_de_atuacao or calcular_curto_circuito. No when-not-to-use guidance or prerequisites are given.

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

A3.9/5.0
Disambiguation5/5

Each tool targets a specific calculation or parameter (e.g., short-circuit, incident energy, cable sizing). Even related tools like partida_motor (voltage dip) and tempo_partida_motor (acceleration time) have distinct purposes. Descriptions clearly differentiate them.

Naming Consistency5/5

All tool names use snake_case and predominantly follow a verb_noun pattern (calcular_, corrigir_, dimensionar_). The few deviations like dano_transformador or k_factor_transformador are still clear and do not break overall consistency.

Tool Count5/5

With 20 tools, the server covers a wide range of electrical engineering calculations without being bloated. Each tool serves a specific purpose, and the count feels well-scoped for the domain.

Completeness4/5

The tool set covers short-circuit, arc flash, protection coordination, cable sizing, and other key areas. Missing advanced topics like load flow are outside the stated scope; only minor gaps like direct relay coordination tools are absent.

Resources