Skip to main content
Glama
tresor4k

macalc

calculate_surface_carrez

Calculate Carrez law surface area for French properties by providing room areas and ceiling heights. Returns usable area, total area, excluded areas, and room details.

Instructions

Calculate Carrez law surface area (French legal measurement). Returns: {carrez_surface_m2, total_surface_m2, excluded_m2, included_rooms, excluded_rooms, note}. See list_bundles for related 'immobilier' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomsYesList of rooms with area and ceiling height

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?

With no annotations, the description should disclose behavioral traits. It mentions the output structure and legal context but does not state side effects, authorization needs, or whether it is read-only. Some transparency is provided through the output fields, but not fully 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?

The description is two sentences, front-loaded with the main purpose, followed by output fields and a pointer to related tools. No redundancy, every sentence earns its place.

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 simplicity (1 parameter, no annotations), the description fully covers the tool's purpose, output, and related resources. It lacks only explicit usage guidelines, but for a calculator tool this is acceptable.

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?

Input schema has 100% coverage, so baseline is 3. The description adds context about the legal measurement and output fields but does not add meaning to the 'rooms' parameter beyond what the schema provides. It is adequate but not enhanced.

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 it calculates Carrez law surface area (French legal measurement) and lists the output fields. It distinguishes itself from sibling calculators by referencing the 'immobilier' bundle, but does not explicitly differentiate from other similar 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 implies usage context (French legal measurement) and suggests looking at list_bundles for related calculators. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor does it name specific alternatives.

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