Skip to main content
Glama
tresor4k

macalc

calculate_density_convert

Convert density values between kg/m³, g/cm³, lb/ft³, and oz/in³. Enter value, source unit, and target unit to get the converted density for engineering, chemistry, or fluid mechanics.

Instructions

Convert density between kg/m³, g/cm³, lb/ft³, and lb/gal. Use for engineering, chemistry, fluid mechanics. Inputs: value, from-unit, to-unit. Returns converted density. See list_bundles for related 'conversions' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesDensity value
from_unitYesSource unit
to_unitYesTarget unit

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 must convey behavioral traits. It states the conversion action and inputs/outputs but does not disclose error handling, unit validation, or any side effects. For a simple conversion tool, this is adequate 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?

The description is three sentences, front-loaded with the primary purpose, and every sentence adds value. It is appropriately sized with no 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 covers core functionality and links to related resources. However, it uses unit abbreviations (kg/m³) that differ from the schema enums (kg_m3), which could cause confusion.

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 description coverage is 100%, so the baseline is 3. The description merely restates the input parameters (value, from-unit, to-unit) without adding new constraints, examples, or clarifications 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 density between specific units (kg/m³, g/cm³, lb/ft³, lb/gal) and lists usage contexts (engineering, chemistry, fluid mechanics). It distinguishes itself from the generic calculate_density sibling by focusing on conversion.

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

Usage Guidelines4/5

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

The description provides usage context ('Use for engineering, chemistry, fluid mechanics') and points to list_bundles for related converters. However, it does not explicitly state when not to use this tool versus other density-related tools.

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