Skip to main content
Glama
tresor4k

macalc

calculate_laundry_cost

Calculate weekly and annual laundry costs including electricity, water, and detergent. Input loads per week and optional consumption details to get cost per load, weekly, and annual totals.

Instructions

Calculate weekly and annual laundry cost (electricity + water + detergent). Returns: {per_load_eur, weekly_eur, annual_eur}. See list_bundles for related 'vie-quotidienne' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loads_per_weekYesLoads per week
electricity_kwh_per_loadNokWh per load (default 1.2)
water_liters_per_loadNoLiters per load (default 50)
detergent_cost_per_loadNoDetergent EUR/load (default 0.30)

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

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

With no annotations, the description must carry the burden. It states the return values but does not disclose behavioral traits such as read-only status, side effects, or permission requirements. For a calculation tool, it fails to assert safety or idempotency.

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 extremely concise, with two sentences covering purpose, return structure, and a pointer to related tools. No wasted words; front-loaded with key information.

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?

The description covers the return object and basic purpose, but lacks usage guidelines and behavioral transparency. For a simple calculator with 4 parameters and no annotations, it is minimally adequate but incomplete.

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 baseline is 3. The description adds no new semantics beyond the schema for each parameter; it only summarizes the overall formula. It does not enhance understanding of parameter usage or constraints.

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 calculates weekly and annual laundry cost including electricity, water, and detergent. It is specific to laundry cost, distinguishing it from other cost calculators, though it does not explicitly differentiate from similar tools like calculate_electricity_cost.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It only mentions 'list_bundles' for related calculators, but does not specify when to choose this tool or when not to.

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