Skip to main content
Glama

Arc Flash Platform — Estudos Elétricos

Energia incidente de arco (IEEE 1584 / NBR 17227)

calcular_energia_incidente
Read-only

Energia incidente (Ei, cal/cm²), LAS e a tabela de EPI da NBR 17227 de um arco elétrico, pelo algoritmo IEEE 1584:2018 / ABNT NBR 17227:2025 da plataforma (208 V–15 kV), que reproduz os exemplos D.1 e D.2 do Anexo D da IEEE 1584:2018. config ∈ {VCB,VCBB,HCB,VOA,HOA}. O campo categoria_epi traz a tabela de EPI que vale para o Ei: diga "Tabela 11" ou "Tabela 12" da NBR 17227 ao usuário, e não "categoria", que é a escala do Anexo IV da NR-10 e da NFPA 70E.

Dois patamares de corrente (IEEE 1584:2018 §4.12): t_arc_s = tempo de eliminação da proteção na corrente de arco PLENA (Iarc); t_arc_reduzido_s = tempo na corrente REDUZIDA (Imin ≈ 0,88·Iarc). Como a corrente reduzida costuma limpar mais devagar (proteção de tempo inverso), o patamar reduzido com frequência GOVERNA o pior caso. Havendo dispositivo com curva inversa, forneça os DOIS tempos. Sem t_arc_reduzido_s, os dois patamares usam o mesmo tempo e vale o MAIOR Ei; em média tensão (> 0,6 kV) o reduzido pode governar mesmo assim (ex.: 13,8 kV, 20 kA, 150 ms).

Os tempos vão em SEGUNDOS (300 ms = 0.3), de 0.01 a 10: fora disso é recusa, porque é erro de unidade ou de vírgula. Abaixo de 0.05 o cálculo sai com aviso. Acima de 2 s o cálculo usa 2 s (IEEE 1584-2018 §6.9.1: quem está no painel consegue se afastar). Em cesto aéreo, com a saída bloqueada ou com a pessoa dentro do equipamento, passe limitar_2s=false, e o cálculo usa o tempo informado. A resposta diz o tempo que valeu: tempo_usado_s, tempo_reduzido_usado_s, tempo_limitado e limite_2s.

larg_mm/alt_mm/prof_mm = invólucro REAL do equipamento (a correção de tamanho da §4.8 muda o Ei). Sem elas, o cálculo usa a caixa de referência de 508 mm e avisos diz que a caixa foi assumida.

Faixa de validade do modelo (NBR 17227 §5.2.2): com largura do invólucro ≤ 4 × gap (VCB/VCBB/HCB) ou distância de trabalho < 305 mm, o Ei sai, mas é EXTRAPOLAÇÃO: a resposta traz fora_da_faixa_do_modelo: true, validado: false e as condições em faixa_do_modelo. Diga isso ao usuário junto do número. avisos traz também o tempo e a baixa potência.

origem_ibf declara de onde veio a Ibf, e a resposta a registra em criterio_ibf: "iec60909_maxima" (a corrente de calcular_curto_circuito ou montar_rede numa chamada anterior, a máxima c_max), "iec60909_minima" ou "tensao_nominal" (c = 1,0 sem K_T). Sem ela, criterio_ibf é "informado_pelo_usuario", e a base é escolha sua, que deve ser dita ao usuário. Gratuito (uso limitado).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tensao_kv": "<tensao_kv>",
      "ibf_ka": "<ibf_ka>",
      "gap_mm": "<gap_mm>",
      "dist_trabalho_mm": "<dist_trabalho_mm>",
      "t_arc_s": "<t_arc_s>"
    },
    "name": "calcular_energia_incidente"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_mmNo
configNoVCB
gap_mmYes
ibf_kaYes
api_keyNo
larg_mmNo
prof_mmNo
t_arc_sYes
tensao_kvYes
limitar_2sNo
origem_ibfNo
dist_trabalho_mmYes
t_arc_reduzido_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / alt_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / alt_mm / default
      Previous value: -508New value: +null
    • removedInput schema / properties / alt_mm / type
      Removed value: -"number"
    • addedInput schema / properties / larg_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / larg_mm / default
      Previous value: -508New value: +null
    • removedInput schema / properties / larg_mm / type
      Removed value: -"number"
    • addedInput schema / properties / limitar_2s
      Added value: +{
      +  "default": true,
      +  "title": "Limitar 2S",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / origem_ibf
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Origem Ibf"
      +}
    • addedInput schema / properties / prof_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / prof_mm / default
      Previous value: -508New value: +null
    • removedInput schema / properties / prof_mm / type
      Removed value: -"number"
  2. Changed4 schema fields changed
    • addedInput schema / properties / alt_mm
      Added value: +{
      +  "default": 508,
      +  "title": "Alt Mm",
      +  "type": "number"
      +}
    • addedInput schema / properties / larg_mm
      Added value: +{
      +  "default": 508,
      +  "title": "Larg Mm",
      +  "type": "number"
      +}
    • addedInput schema / properties / prof_mm
      Added value: +{
      +  "default": 508,
      +  "title": "Prof Mm",
      +  "type": "number"
      +}
    • addedInput schema / properties / t_arc_reduzido_s
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "T Arc Reduzido S"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description adds a lot beyond that: input validation ranges (0.01–10 s rejected, <0.05 s warns), the 2 s clamp with its engineering rationale (§6.9.1), the reduced-current second plateau governing the worst case, and explicit extrapolation flags (fora_da_faixa_do_modelo, validado, faixa_do_modelo). It also discloses 'Gratuito (uso limitado)' and names the response fields (tempo_usado_s, tempo_limitado, limite_2s, criterio_ibf), which is well beyond what the annotations carry.

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?

It is long for a tool description, but front-loaded with the outcome and then organized into coherent blocks (plateaus, time rules, enclosure, model validity, Ibf provenance). Each paragraph carries distinct decision-relevant content; some sentences, such as the worked 13,8 kV / 20 kA example, could be trimmed without loss.

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

Completeness4/5

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

For a 13-parameter engineering calculation with no output schema, the description covers the model validity envelope, the two-current-plateau logic, the time-limiting policy and the key response fields, which is close to what an agent needs. Residual gaps are that api_key is never explained despite the 'uso limitado' note, and LAS is used without expansion.

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?

Schema coverage is 0%, so the description must carry the load, and it mostly does: it supplies the config domain {VCB,VCBB,HCB,VOA,HOA} that the schema leaves as an unconstrained string, defines t_arc_s vs t_arc_reduzido_s (Iarc vs Imin ≈ 0,88·Iarc) with unit and range rules, explains limitar_2s, the real-enclosure larg_mm/alt_mm/prof_mm versus the 508 mm default, and enumerates the origem_ibf values with their footing (c_max, c_min, c=1,0). Only tensao_kv, gap_mm, dist_trabalho_mm, ibf_ka and api_key rely on unit-suffixed names alone, which keeps it from being exhaustive but is far above the low-coverage baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening states a concrete verb and resource: compute incident energy (Ei, cal/cm²), arc-flash boundary (LAS) and the NBR 17227 PPE table from an electric arc, using IEEE 1584:2018 / ABNT NBR 17227:2025. The 208 V–15 kV range implicitly bounds it against the sibling calcular_energia_incidente_hv, but that sibling is never named, so the differentiation is inferred rather than stated.

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?

Usage context is rich but operational rather than tool-selection oriented: it says to supply both t_arc_s and t_arc_reduzido_s when an inverse-curve device exists, to pass limitar_2s=false for aerial baskets or blocked exits, and to feed origem_ibf from a prior calcular_curto_circuito / montar_rede call. It never states when not to use this tool or when a sibling should be preferred (e.g., above 15 kV).

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.

Resources