Skip to main content
Glama
tresor4k

macalc

calculate_insulation_r

Compute R-value (m²·K/W) from thickness (mm) and thermal conductivity (W/m·K) for insulation specification compliant with RT2020/RE2020 standards. Input thickness and λ to get thermal resistance.

Instructions

Compute thermal resistance R = thickness/lambda. Use for insulation specification (RT2020/RE2020). Inputs: thickness m, conductivity λ W/m·K. Returns R-value m²·K/W. See list_bundles for related 'construction' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thickness_mmYesThickness mm
lambdaYesConductivity W/(m.K)

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 must carry the full burden. It explains the calculation formula and what inputs/outputs are expected, but it fails to disclose any behavioral traits such as handling of edge cases (e.g., zero or negative inputs) or any side 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?

The description is three sentences, front-loaded with the formula and purpose. It is concise and each sentence adds information, though the unit error mars the efficiency.

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?

Given the existence of a sibling tool 'calculate_insulation_r_value', the description should explicitly differentiate but does not. Additionally, the unit mismatch reduces completeness. The presence of an output schema partially compensates, but the description could be more thorough.

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?

The description states inputs as 'thickness m' but the schema uses 'thickness_mm' (millimeters). This unit inconsistency is misleading and reduces the value added beyond the schema, despite 100% schema coverage. The description also mentions 'conductivity λ W/m·K' which matches the schema.

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 thermal resistance using a specific formula and for a specific regulatory context (RT2020/RE2020). However, it does not differentiate from the sibling tool 'calculate_insulation_r_value', which appears to have a very similar name and purpose.

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 specifies when to use the tool ('Use for insulation specification (RT2020/RE2020)') and mentions 'See list_bundles for related "construction" calculators', but it does not explicitly indicate situations where this tool is not appropriate or suggest direct alternatives like the sibling tool.

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