Skip to main content
Glama
tresor4k

macalc

calculate_international_shipping

Estimate international shipping cost and delivery time by entering parcel weight, dimensions, and origin zone. Returns cost range and lead time, ideal for e-commerce and personal shipping.

Instructions

Estimate international shipping cost and delivery time by carrier and weight. Use for e-commerce or expat shipping. Inputs: from-country, to-country, weight kg, dimensions. Returns cost range and lead time. See list_bundles for related 'voyage' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weight_kgYesActual parcel weight in kg
dimensions_cmYesParcel dimensions in cm (length, width, height)
from_zoneYesDestination zone

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 are provided, so the description must fully disclose behavior. It states 'estimate' but does not confirm it is read-only, safe, or require any authentication. No mention of error handling, rate limits, or side effects, which is insufficient for a tool with no annotations.

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

Conciseness3/5

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

The description is brief with two sentences and a pointer, which is concise, but includes unnecessary inaccuracies that could be avoided. It is front-loaded but not optimally structured.

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

Completeness2/5

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

Despite an output schema existing, the description only mentions 'cost range and lead time'. It omits the fact that 'from_zone' is used instead of country names, and does not explain the format of dimensions or weight. The tool's purpose is partially complete but lacks sufficient detail given the complexity.

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?

Although schema coverage is 100% with descriptions, the tool description introduces 'from-country, to-country, carrier' which are not in the schema, potentially misleading. It adds little value beyond the schema and inaccurately describes parameters.

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?

The description clearly states the tool estimates international shipping cost and delivery time, which distinguishes it from many sibling calculators. However, it mentions 'by carrier and weight' and 'from-country, to-country' whereas the schema only has 'from_zone' and no carrier parameter, causing slight inaccuracy.

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 use for e-commerce or expat shipping and references list_bundles for related calculators, providing some guidance. However, it does not specify when not to use it or mention alternatives like calculate_shipping_volumetric, limiting comprehensiveness.

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