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.3/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=true, so description need not reiterate safety. Adds context about free but limited usage. Does not contradict annotations. Adequate but no further behavioral details (e.g., output format, prerequisites).

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?

Description is reasonably concise given technical content, but includes some redundant phrasing (e.g., mentions inrush twice). Front-loaded with purpose. Could be more structured with bullet points for parameter options.

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?

With 10 parameters, no output schema, and complex technical context, description lacks explanation of required parameters and return value. Agent cannot infer output format or how curve is presented. Incomplete for effective use.

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%, requiring description to compensate. Description explains 5 optional parameters (fases, frequencia_falta, tipo, t_inrush_ms, ligacao) but fails to describe 3 required parameters (Sn_kVA, Vn_kV, Vcc_pct) and other optional ones (api_key, k_inrush). Insufficient for an agent to understand required inputs.

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?

Description clearly states the tool computes a transformer damage curve per IEEE C57.109/C57.12.59, specifying purpose (coordinate upstream protection) and parameters. It distinguishes from sibling tools like calcular_curto_circuito or dimensionar_tc which have different functions.

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?

Description implies usage for protection coordination but does not explicitly state when to use or avoid this tool vs alternatives. No direct comparison to sibling tools or mention of alternative scenarios.

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