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.4/5.0

Behavior4/5

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

Annotations show readOnlyHint=true, which aligns with a calculation tool. The description adds behavioral context: it uses a composite curve, optional parameters activate specific segments, and it is free with limited use. No contradictions.

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 with clear sections (purpose, pipeline, manual, catalog, cost). It is somewhat lengthy but every sentence adds value. Could be slightly more concise.

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 10 parameters, no output schema, and sibling tools, the description explains the output usage (tempo_s as t_arc_s) and references related steps. It is sufficiently complete for the tool's complexity.

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 description coverage, the description includes a detailed 'MANUAL' section explaining each parameter (pickup_A, curva, tms, etc.), their types, defaults, and purpose. This fully compensates for the schema gap.

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 protection device operation time using a 4-segment curve, referencing specific standards. It also explains its role as the link between short-circuit calculation and incident energy, distinguishing 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 shows the pipeline order (calcular_curto_circuito -> tempo_de_atuacao -> calcular_energia_incidente), indicating when to use it. It also mentions limited usage, but lacks explicit exclusions or alternatives.

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?