Skip to main content
Glama
tresor4k

macalc

calculate_cable_section

Calculates required electrical cable cross-section (mm²) for residential wiring per NF C 15-100. Enter power (kW), voltage, cable length, and max voltage drop to get the section.

Instructions

Compute electrical cable cross-section (mm²) per NF C 15-100. Use for residential wiring. Inputs: power kW, voltage, length, max voltage drop %. Returns required section. See list_bundles for related 'construction' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
power_wYesPower W
voltageNoVoltage
length_mYesCable length m
max_drop_pctNoMax voltage drop %

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

No annotations provided, so description carries full burden. It only states the function (computes cross-section) but does not disclose any side effects, limits, or behaviors beyond the basic operation. Adequate for a simple calculator but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise: two sentences that front-load the purpose and include a pointer to related tools. Every sentence provides value without redundancy.

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's simplicity and the presence of an output schema, the description adequately covers the standard, use case, and inputs. Could mention that the result is in mm², but output schema likely covers return format.

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

Parameters3/5

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

While schema coverage is 100% and description mentions the inputs, it says 'power kW' whereas the schema uses watts ('power_w'), causing a minor inconsistency. Given good schema coverage, the description adds little extra meaning beyond enumerating inputs.

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?

Clearly states the verb 'Compute', resource 'electrical cable cross-section', standard 'NF C 15-100', and context 'residential wiring'. Differentiates from siblings by mentioning specific standard, but sibling 'calculate_cable_section_electrical' exists, so not fully distinct.

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?

Explicitly says 'Use for residential wiring', which is a usage context, but does not specify when not to use or provide direct alternatives beyond a vague reference to 'list_bundles' for related calculators.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server