Skip to main content
Glama
tresor4k

macalc

calculate_moving_cost_detailed

Estimate moving cost based on volume (m³), distance (km), floor level, and elevator availability. Returns base cost, total cost in EUR, and a note.

Instructions

Estimate detailed moving cost based on volume, distance and floor. Returns: {base_cost, total_cost_eur, note}. See list_bundles for related 'immobilier' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
volume_m3YesVolume of goods to move in m3
distance_kmYesMoving distance in km
floorNoFloor number (default 0 = ground floor)
elevatorNoWhether elevator is available (default true)

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 the burden. It discloses the return structure (base_cost, total_cost_eur, note) but does not mention side effects, safety, or any behavioral constraints beyond being a calculation tool. This is adequate but not explicit.

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 two sentences, front-loaded with the core purpose, and efficiently includes the output format and sibling reference. No unnecessary words.

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?

For a calculation tool with 4 parameters and an output schema, the description covers the essential: what it does, what it returns, and a hint to siblings. It does not cover error handling or edge cases, but the output schema fills in details. Adequate for agent invocation.

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% description coverage, so the schema already documents each parameter. The description adds the output structure but does not provide additional parameter meaning beyond what the schema offers. Baseline score 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 'Estimate detailed moving cost' and lists the key parameters (volume, distance, floor). It distinguishes itself by referencing 'immobilier' calculators and pointing to list_bundles for related tools, differentiating among many sibling tools.

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 by mentioning 'related immobilier calculators' and directing to list_bundles. However, it does not explicitly state when to use this tool versus alternatives, limiting the guidance.

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