Arc Flash Platform — Estudos Elétricos

Energia incidente > 15 kV — triagem (OSHA / Lee / EPRI)

calcular_energia_incidente_hv

Read-only

Energia incidente para sistemas > 15 kV — FORA do IEEE 1584:2018 / NBR 17227 (arco ao ar livre fase-terra). É TRIAGEM, NÃO laudo: o motor IEEE 1584 da plataforma NÃO é usado; gap e configuração de eletrodos não se aplicam.

metodo ∈ {osha (padrão), lee, epri}: • osha — OSHA 1910.269 Apêndice E, Tab. 6/7 (base ArcPro). tipo_trabalho ∈ {luva (Tab.6, 4–46 kV), vara (Tab.7, 4–800 kV)}. Devolve a BANDA de EPI conservadora (≤4/5/8/12 ou >12 cal/cm²), não um ponto. • lee — cota TEÓRICA superior; exige dist_trabalho_mm. • epri — modelo de alta tensão; exige dist_trabalho_mm + comprimento_arco_m (vão físico fase-terra, em metros). Gratuito (uso limitado).

Input Schema

TableJSON Schema

Name	Required	Default
`t_ms`	Yes
`ibf_ka`	Yes
`metodo`	Yes
`api_key`	No
`tensao_kv`	Yes
`tipo_trabalho`	No	luva
`dist_trabalho_mm`	No
`comprimento_arco_m`	No

TDQS

A4.5/5.0

Behavior4/5

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

No contradiction with annotations (readOnlyHint). Description adds context: it's a screening tool with limited free usage, not a full compliant calculation. Does not mention if any side effects exist, but as a read-only calculation, that's acceptable.

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?

Well-structured with clear sections, but could be slightly more concise. Front-loaded purpose, then method details, then usage note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (8 params, 3 methods, no output schema), the description is comprehensive: covers method-specific behavior, output for OSHA (EPI band), and limitations. Missing explicit output schema but sufficiently described.

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

Parameters5/5

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

Despite 0% schema coverage, description explains each method's parameters in detail, including default values and conditions. Required params are implied; api_key is noted as optional via schema but not explained.

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?

Title and description clearly state it calculates incident energy for >15 kV systems, outside IEEE 1584, as a screening tool. Distinguishes from sibling 'calcular_energia_incidente' which likely covers <=15 kV.

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?

Explicitly states when to use (>15 kV, screening, not full laudo) and method selection criteria. Lacks explicit mention of alternatives but the sibling list provides context.

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

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

Need Help?