MaCalculatriceEnLigne

calculate_brick_count

Compute bricks or blocks needed for a wall including waste margin. Use for masonry projects. Inputs: wall dimensions, brick size, waste %. Returns brick count and pallets. See list_bundles for related 'construction' calculators.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Brick type	parpaing
`height_m`	Yes	Wall height m
`length_m`	Yes	Wall length m

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

C2.9/5.0

Behavior3/5

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

The description states it includes waste margin and returns brick count and pallets, but it references inputs (brick size, waste %) that are not present in the input schema. This discrepancy harms transparency. Without annotations, it carries the full burden but is partially accurate.

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?

The description is short and front-loaded with the main purpose. However, it includes extraneous input mentions that are not supported, which slightly detracts from its conciseness. Overall, it is efficient but could be more accurate.

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?

Given the simplicity of the tool (3 parameters, output schema exists), the description should fully cover behavior. It mentions output but fails to describe the type parameter or align with the schema. The waste margin claim is unsubstantiated. This incompleteness reduces its utility.

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

Parameters1/5

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

Schema coverage is 100%, so baseline is 3, but the description adds misleading information by mentioning 'brick size' and 'waste %' which are not in the schema. This contradicts the schema and reduces clarity. The description should align with the defined 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 computes bricks or blocks needed for a wall, including waste margin, and references a related tool for more calculators. It specifies the domain (masonry projects) and the main objective, though it could better differentiate from other calculate_* tools.

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 explicitly says 'Use for masonry projects' and directs to list_bundles for related calculators, providing some usage context. However, it does not mention when not to use this tool or provide alternatives beyond the bundle tool.

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.