Skip to main content
Glama
tresor4k

macalc

calculate_delivery_cost

Estimate delivery cost in EUR based on package weight, distance, and service type (standard or express). Returns cost, formula, and note.

Instructions

Estimate shipping cost from weight, distance and service (standard vs express). Returns: {cost_eur, formula, note}. See list_bundles for related 'vie-quotidienne' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weight_kgYesPackage weight kg
distance_kmYesDelivery distance km
typeNoService levelstandard

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 disclose behavioral traits. It states the tool estimates cost and returns an object, but lacks details on idempotency, side effects, authentication needs, or data freshness. For a simple calculator, this is minimally adequate but not comprehensive.

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: first states the core purpose, second adds related tool information and output structure. No unnecessary words; front-loaded with essential 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 tool's simplicity (3 parameters, calculator), the description covers purpose, inputs, output, and a pointer to related calculators. It lacks explicit unit clarification or disclaimers, but overall is sufficient for an agent to use the tool correctly.

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?

Schema coverage is 100% with descriptions for all three parameters. The description reiterates the parameter names but adds no new semantics (e.g., units, constraints, or relationships). It mentions the return structure but that is output, not parameter-related. Baseline 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 estimates shipping cost based on weight, distance, and service type, which distinguishes it from other calculator tools. Despite missing a title, the description is specific and action-oriented.

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

Usage Guidelines2/5

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

The description only hints at related tools via 'See list_bundles for related 'vie-quotidienne' calculators' but offers no explicit guidance on when to use this tool versus any of the many sibling calculator tools like calculate_shipping_volumetric or calculate_international_shipping. No when-not-to or alternative usage contexts.

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