MaCalculatriceEnLigne

calculate_excavation

Compute excavation volume (m³) and truck loads needed for a foundation, pool, or trench. Use for construction. Inputs: length, width, depth (m), bulking factor. Returns m³ to remove and 8m³-truck count. See list_bundles for related 'construction' calculators.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`depth_m`	Yes	Depth in meters
`width_m`	Yes	Width in meters
`length_m`	Yes	Length in meters
`soil_type`	No	Soil type (swell: normal=1.25, rocky=1.50, clay=1.30)	normal

Output Schema

TableJSON Schema

Name	Required	Description
`result`	No	Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
`source`	No	Authoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
`formula`	No	Human-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
`reference_url`	No	Link to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It states the tool computes and returns volume and truck count, but lacks details on error handling, input constraints, or side effects. It is adequate but not rich.

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 highly concise: two sentences with clear purpose and a third referencing related tools. Every sentence adds value, and the structure is front-loaded.

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 complexity of the tool (4 parameters, output schema exists), the description covers the core functionality and points to related tools. It lacks detailed explanation of the soil_type's relationship to bulking factor, but overall it is fairly complete.

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 parameters. The description adds context by listing inputs (length, width, depth, bulking factor) and outputs, but it inaccurately refers to 'bulking factor' instead of the soil_type enum. This is a minor inconsistency.

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 computes excavation volume and truck loads for foundation, pool, or trench. It uses a specific verb ('Compute') and identifies the resource. However, it does not explicitly differentiate from sibling tools like calculate_pool_volume, but points to 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 Guidelines3/5

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

The description says 'Use for construction' and references list_bundles for related calculators, implying when to use. However, it does not explicitly state when not to use or provide alternatives, leaving some ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MaCalculatriceEnLigne tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.