Skip to main content
Glama
tresor4k

macalc

calculate_string_tension

Calculate guitar or bass string tension in pounds, kilograms, and Newtons by entering scale length, target tuning frequency, and string gauge.

Instructions

Calculate guitar or bass string tension in pounds, kilograms and Newtons. See list_bundles for related 'musique' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scale_length_inchesYesInstrument scale length in inches (e.g. 25.5 for Fender Stratocaster)
frequency_hzYesTarget tuning frequency in Hz (e.g. 329.63 for E4)
gauge_inchesYesString gauge in inches (e.g. 0.010 for a light gauge high E)

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 are provided, so the description carries full burden. It does not disclose behavioral traits such as being a pure calculation (no side effects), error handling, or performance constraints. For a calculator, this is acceptable but minimal.

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?

Two sentences: the first concisely states the tool's purpose and outputs, the second guides to related tools. No wasted words, front-loaded with key information.

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 simple parameter set (3 numeric inputs) and existence of an output schema, the description is largely complete. It covers the calculation, units, and related tools. Minor gap: does not mention any constraints like unit consistency, but schema covers ranges.

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 input schema has 100% coverage with detailed parameter descriptions (including examples). The description adds no additional semantic value beyond what the schema already provides, so baseline score of 3 is appropriate.

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 calculates guitar or bass string tension, and specifies the output units (pounds, kilograms, Newtons). It references a sibling tool (list_bundles) for related calculators, distinguishing it from other similar tools on the server.

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 by specifying the calculation domain, but does not explicitly state when to use this tool versus alternatives. The reference to list_bundles provides some context but no exclusions or direct comparisons.

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