Skip to main content
Glama
tresor4k

macalc

calculate_wire_gauge_convert

Convert AWG wire gauge to diameter (mm), cross-sectional area, resistance (ohms/m), and maximum current capacity. Essential for selecting wire size in electrical projects.

Instructions

Convert AWG wire gauge to diameter (mm) and resistance (ohms/m). Use for electrical projects. Inputs: AWG number. Returns diameter, area, resistance, max current. See list_bundles for related 'conversions' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
awgYesAWG gauge number

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.
Behavior4/5

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

No annotations provided, so description carries full burden. It clearly states inputs, outputs, and the conversion nature. No side effects are mentioned, but as a calculation tool, this is acceptable.

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 relatively concise, covering purpose, usage, inputs, outputs, and related tools in a few sentences. It could be more structured but is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, simple conversion, output schema present), the description adequately covers all necessary information: inputs, outputs, usage context, and related tools.

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?

The schema already describes the parameter (awg, integer 0-40). The description repeats 'Inputs: AWG number' but adds no new semantic meaning beyond the schema.

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 converts AWG wire gauge to diameter and resistance, listing specific outputs. It distinguishes from sibling calculators by focusing on electrical wire gauge conversion.

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 suggests using for electrical projects and points to list_bundles for related calculators, but does not explicitly state when to use this tool over others or when not to use it.

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