Arc Flash Platform — Estudos Elétricos

Grupo gerador — degrau de carga (ISO 8528)

grupo_gerador

Read-only

Afundamento transitório de tensão ao aplicar um degrau de carga a um grupo gerador (ISO 8528-5, etapa 1: tensão), via reatância transitória X'd. modo ∈ {bloco (degrau_kVA+degrau_fp), motor (motor_kW, partida DOL)}. XR = X/R da X'd (ângulo da queda). cabo_mm2+cabo_m = alimentador gerador→carga (a queda no cabo soma no ΔV). dv_limite_pct sobrepõe o limite da classe — OBRIGATÓRIO para classe_iso="G4" (limite por acordo). motor_fp_rotor_bloqueado = FP de partida (modo motor). Gratuito (uso limitado).

Input Schema

TableJSON Schema

Name	Required	Default
`XR`	No
`modo`	No	bloco
`Sn_kVA`	Yes
`cabo_m`	No
`xd_pct`	No
`api_key`	No
`cabo_mm2`	No
`motor_kW`	No
`tensao_V`	Yes
`degrau_fp`	No
`classe_iso`	No	G2
`degrau_kVA`	No
`motor_Ip_In`	No
`dv_limite_pct`	No
`motor_fp_rotor_bloqueado`	No

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true. The description adds that the tool is free with limited usage and explains the calculation methodology (via transient reactance, cable drop impact), providing context beyond 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 dense and efficient, using a single paragraph with line breaks. Each sentence adds value without redundancy. It could be structured for easier scanning, but it's concise.

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 (15 parameters, no output schema), the description explains the calculation context well but fails to specify the output format or return values. It also omits error conditions and limitations beyond 'uso limitado'.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates by explaining many key parameters (e.g., modo, XR, cabo_mm2, dv_limite_pct, motor_fp_rotor_bloqueado) and their roles. Not all 15 parameters are detailed, but the essential ones for usage are covered.

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 title and description clearly state the tool calculates transient voltage dip when applying a load step to a generator set per ISO 8528-5. It specifies two modes (block and motor) and distinguishes from sibling tools like partida_motor and calcular_curto_circuito.

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 explains the two operational modes and the parameters for each, giving clear context for when to use each mode. However, it does not explicitly compare with alternatives or state when not to use the tool.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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

Need Help?