Skip to main content
Glama

Arc Flash Platform — Estudos Elétricos

Correção de fator de potência (REN 1.000)

corrigir_fator_potencia
Read-only

Dimensiona o banco de capacitores para corrigir o fator de potência à meta (REN ANEEL nº 1.000; FP-alvo padrão 0,92). Com tensao_kV também dá a corrente nominal do banco e a norma (IEC 60831/60871). Un_cap_kV = tensão de placa do capacitor: se ele opera abaixo da Un, entrega MENOS kvar (derating Q∝V²) e a correção real cai — informe p/ não superestimar. carga_min_pct = carregamento mínimo (%): dispara o alerta de SOBRECORREÇÃO capacitiva (banco fixo em carga leve → FP capacitivo, faturável). scc_MVA = curto na barra do banco → inrush de manobra e a corrente de PROJETO da proteção/cabo do banco (1,5·In BT, IEEE C37.012). Gratuito.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNo
fp_metaNo
scc_MVANo
fp_atualYes
Un_cap_kVNo
tensao_kVNo
potencia_kWYes
carga_min_pctNo

TDQS

A4.3/5.0
Behavior5/5

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

The description discloses detailed behavioral traits: derating due to voltage, overcorrection alert at light load, inrush current for protection design. Annotations only provide readOnlyHint and title, so the description adds significant context beyond them.

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 concise (5-6 sentences), front-loads the main purpose, and packs technical details without excessive verbosity. It could be slightly more structured, but it is well within acceptable limits.

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 no output schema and 8 parameters, the description covers the main behavior, parameter effects, and outputs (capacitor size, optional current, standard, alerts). It is reasonably complete for a calculation tool.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates well by explaining optional parameters (tensao_kV, Un_cap_kV, carga_min_pct, scc_MVA) and their effects. However, required parameters (potencia_kW, fp_atual) are not explicitly described, and api_key is not mentioned.

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 capacitor banks for power factor correction to a target (0.92) according to REN ANEEL 1.000. It uses a specific verb ('dimensiona') and resource ('banco de capacitores'), and it distinguishes from sibling tools by focusing on power factor correction.

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

Usage Guidelines3/5

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

The description implies usage for power factor correction to meet regulatory standards but does not explicitly state when to use this tool versus alternatives. No direct comparison or exclusion criteria are provided.

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.

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