Arc Flash Platform — Estudos Elétricos

Dimensionamento de cabo BT (NBR 5410)

dimensionar_cabo

Read-only

Dimensiona a seção de um cabo BT pela ABNT NBR 5410: ampacidade (Tab. 36-39 + fatores), queda de tensão, coordenação de sobrecarga (§5.3.4.1), neutro e PE. sistema ∈ {1FN,2F,3F,3FN}; metodo = método de instalação (A1,A2,B1,B2,C,D,E,F,G); material ∈ {Cu,Al}; isolacao ∈ {PVC,EPR}. icc_quadro_kA = Icc presumida no quadro de origem. n_circuitos_agrupados = nº de circuitos no mesmo eletroduto/leito (aplica o fator de agrupamento da Tab. 42 — reduz a ampacidade); arranjo ∈ {feixe,camada}. disjuntor_In_A/curva_disjuntor (B,C,D) = o dispositivo REAL instalado (sem eles, assume o menor MCB ≥ Ib, curva C). Gratuito.

Input Schema

TableJSON Schema

Name	Required	Default
`fp`	No
`metodo`	No	B1
`api_key`	No
`arranjo`	No	feixe
`sistema`	No	3FN
`isolacao`	No	PVC
`material`	No	Cu
`tensao_V`	Yes
`potencia_W`	Yes
`comprimento_m`	Yes
`icc_quadro_kA`	No
`queda_max_pct`	No
`disjuntor_In_A`	No
`curva_disjuntor`	No	C
`temp_ambiente_C`	No
`n_circuitos_agrupados`	No

TDQS

A3.9/5.0

Behavior4/5

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

The description adds behavioral context beyond annotations: it details the calculation method (ampacity, voltage drop, coordination) and parameter effects. No side effects are mentioned, consistent with readOnlyHint.

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 information-dense and concise but lacks structure (single paragraph). Could use bullet points for readability, but no waste.

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?

The description covers parameters thoroughly but does not explain return values or output format. Given no output schema, this is a gap, though complexity is high.

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 coverage, the description compensates by explaining each parameter's meaning, units, and default behavior (e.g., 'assume o menor MCB ≥ Ib, curva C'). This adds significant value.

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 the tool dimensions a BT cable section according to NBR 5410, specifying tables and factors. It distinguishes from sibling tools like calcular_curto_circuito by focusing on cable sizing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lacks explicit guidance on when to use this tool versus alternatives. It provides no context like 'Use for sizing cables in low voltage installations' or exclusions.

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?