Arc Flash Platform — Estudos Elétricos

Tempo de atuação da proteção (IEC 60255-151 / IEEE C37.112)

tempo_de_atuacao

Read-only

Tempo de atuação de um dispositivo de proteção à corrente de falta, pela curva composta 4-segmentos do motor da plataforma (IEC 60255-151 / IEEE C37.112): 51 inversa · 50 curto-tempo · 50 instantânea. É o ELO entre o curto e o arco: encadeie calcular_curto_circuito → tempo_de_atuacao → calcular_energia_incidente (o tempo_s daqui é o t_arc_s, o parâmetro mais difícil de estimar à mão).

MANUAL (universal): pickup_A = pickup do 51 (relé: RTC×tap; disjuntor: Ir); curva ∈ IEC/IEEE; tms = TMS (IEC) ou time-dial (IEEE); instantaneo_A+t_disjuntor_ms (50 instantânea) e curto_tempo_A+t_curto_tempo_ms (50 temporizada) são opcionais — sem eles, só a inversa opera. CATÁLOGO: device_id de MCCB/ACB (use listar_dispositivos). Gratuito (uso limitado).

Input Schema

TableJSON Schema

Name	Required	Default
`tms`	No
`curva`	No	IEC Very Inverse (VI)
`api_key`	No
`pickup_A`	No
`device_id`	No
`curto_tempo_A`	No
`instantaneo_A`	No
`t_disjuntor_ms`	No
`corrente_falta_A`	Yes
`t_curto_tempo_ms`	No

TDQS

A4.2/5.0

Behavior3/5

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

The description mentions it is a calculation tool with limited free usage, but does not add behavioral context beyond what the readOnlyHint annotation already implies. No contradictions with 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 well-structured and front-loaded, starting with the purpose and chain context. It is moderately long but every sentence adds value; could be slightly more concise but is appropriate for the complexity.

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?

Given the tool has 10 parameters, no output schema, and no enum constraints, the description provides sufficient context including the chain usage, manual vs catalog modes, and cost information. It covers the essential aspects for an agent to select and invoke the tool correctly.

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?

With 0% schema description coverage, the description compensates fully by explaining the purpose of each key parameter (pickup_A, curva, tms, instantaneo_A, t_disjuntor_ms, curto_tempo_A, t_curto_tempo_ms, device_id) and the optional behavior for the 50 instantaneous and short-time elements.

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 calculates the operating time of a protection device using specific curves (IEC/IEEE) and positions it within a three-step chain (calcula_curto_circuito → tempo_de_atuacao → calcular_energia_incidente), differentiating it from sibling tools.

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 explicitly states when to use the tool (after short-circuit calculation, before incident energy) and provides both manual and catalog usage modes. However, it does not explicitly state when not to use it or list alternatives beyond the chain.

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?