Skip to main content
Glama
tresor4k

macalc

calculate_roof_truss

Calculate roof truss dimensions, rafter length, and material quantities for a pitched roof. Input span, pitch angle, truss spacing, and load for accurate construction estimates.

Instructions

Calculate roof truss dimensions, rafter length and material quantities for a pitched roof. See list_bundles for related 'construction' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
span_mYesTotal roof span in meters (full width)
pitch_degreesYesRoof pitch angle in degrees
spacing_cmNoDistance between trusses/rafters in cm (default 60cm)
load_kg_m2NoTotal roof load in kg/m² including snow, wind and tiles (default 150)

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 carries full burden. It adequately conveys the tool's purpose as a calculator but does not disclose additional behavioral traits like read-only nature, side effects, or prerequisites beyond what is implied by the input schema.

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 a single concise sentence with no wasted words, effectively communicating its purpose and a reference to related tools. It is well-structured and 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 tool is a calculator with 4 parameters and an output schema, the description sufficiently covers the tool's scope. It could be slightly improved by mentioning that outputs are calculated or referencing the output schema, but is largely 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 description coverage is 100%, so the schema already documents all parameters. The tool description does not add any extra parameter-level meaning beyond what is in the schema, achieving baseline 3.

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?

The description clearly states the tool calculates roof truss dimensions, rafter length, and material quantities for a pitched roof, using a specific verb and resource. It also distinguishes itself from siblings by referencing list_bundles for related construction 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?

The description provides context for use by specifying it's for pitched roof calculations and references list_bundles for other construction calculators, but lacks explicit instructions on when not to use or clear differentiation from similar tools.

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