Skip to main content
Glama
tresor4k

macalc

calculate_curtain_fabric

Calculate fabric meters needed for sewing curtains, accounting for window dimensions, fullness ratio, number of panels, and pattern repeat. Input your measurements to determine the exact fabric length to purchase.

Instructions

Compute fabric meters needed for curtains, including hems and pattern repeat. Use for sewing. Inputs: window dimensions, fullness, pattern repeat. Returns fabric length to buy. See list_bundles for related 'textile-mode' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
window_width_cmYesWindow width cm
window_height_cmYesWindow height cm
fullness_ratioNoFullness ratio (2 = double fullness)
num_panelsNoNumber of curtain panels

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.
Behavior4/5

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

No annotations provided, but the description explains the calculation includes hems and pattern repeat and returns fabric length, adding behavioral context beyond the name.

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?

Two concise sentences front-load the purpose and direct to related tools, with no unnecessary words.

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?

Description covers basic purpose and output, but the missing pattern repeat parameter in schema undermines completeness; output schema exists but not described.

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?

Schema covers 100% of parameters with descriptions, but the description mentions 'pattern repeat' as an input, which is not in the schema, causing discrepancy and potential confusion.

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 computes fabric meters for curtains including hems and pattern repeat, and distinguishes from sibling tools by referencing 'textile-mode' 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 says 'Use for sewing' and directs to list_bundles for related calculators, providing clear context on when to use this tool, though no explicit exclusions.

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