Skip to main content
Glama
tresor4k

macalc

calculate_shipping_volumetric

Compute volumetric (dimensional) weight for shipping using length, width, height in cm and actual weight. Carriers bill the higher of actual weight and dim weight. Standard divisor: 5000 for air, 6000 for ground.

Instructions

Compute volumetric (dimensional) weight for shipping. Carriers bill the higher of actual and dim weight. Inputs: L×W×H cm, divisor (5000 air, 6000 ground). Returns dim weight kg. See list_bundles for related 'finance-universal' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
length_cmYesLength cm
width_cmYesWidth cm
height_cmYesHeight cm
actual_kgYesActual weight kg

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

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

No annotations provided; description mentions a divisor parameter not present in input schema, creating inconsistency and confusion about tool behavior. Also fails to explain role of actual_kg.

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?

Two sentences plus reference, front-loaded with purpose, but includes misleading divisor info that could be omitted or corrected.

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

Completeness3/5

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

Mentions return value (dim weight kg) but does not explain how actual_kg is used or that the tool compares actual vs dim weight. With output schema present, description could be more complete.

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

Parameters2/5

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

Schema covers all parameters with descriptions; description adds misleading info about divisor not in schema, and does not clarify usage of actual_kg.

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 it computes volumetric weight for shipping, differentiating it from other calculators by referencing list_bundles for related calculators.

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?

Provides inputs and output, and hints at divisors for air/ground, but does not explicitly exclude other scenarios or mention when not to use this tool.

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