Skip to main content
Glama
tresor4k

macalc

calculate_brick_count

Compute bricks or blocks for a wall including waste margin. Input wall length, height, and brick type. Returns brick count and pallet quantity for masonry projects.

Instructions

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
NameRequiredDescriptionDefault
length_mYesWall length m
height_mYesWall height m
typeNoBrick typeparpaing

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 provided. Description does not disclose side effects, but as a calculator it is assumed read-only. Could be improved by stating it has no destructive effects.

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?

Two sentences plus sibling reference. Concise and front-loaded, but second sentence could be more structured.

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

Completeness3/5

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

Output schema exists but is not described. Description covers main purpose but omits important details like default brick type (parpaing) and missing waste parameter. Adequate but has gaps.

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?

Description mentions 'brick size' and 'waste %' as inputs, but schema only includes length_m, height_m, and type. This inconsistency may confuse agents. Schema coverage is 100%, but description adds misleading information.

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?

Description clearly states 'Compute bricks or blocks needed for a wall including waste margin' and specifies inputs and outputs. Differentiates from sibling tools by referencing '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 Guidelines4/5

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

States 'Use for masonry projects' and directs to 'list_bundles' for related calculators. Lacks explicit when-not-to-use or alternative tool names, but provides adequate context.

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