Skip to main content
Glama
tresor4k

macalc

calculate_laundry_cost

Calculate weekly and annual laundry costs based on loads per week, including electricity, water, and detergent. Returns cost per load and total.

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

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

No annotations provided; description states it returns cost values. For a computation tool, it's adequate but doesn't disclose any special behaviors or side effects beyond the calculation.

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: first states purpose and components, second states return shape and points to related bundle. No wasted words.

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?

Description covers purpose, return shape, and related tools. For a simple calculator with defaults and output schema, it is complete enough. Slightly more detail on default behavior could be added but not essential.

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 covers 100% of parameters with descriptions; description adds context on return shape and components but doesn't add significant meaning beyond schema.

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?

Description clearly states the tool calculates weekly and annual laundry cost with components (electricity, water, detergent). It mentions related calculators via 'list_bundles', distinguishing it from sibling calculator tools.

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?

Description implies usage for laundry cost estimation and references 'list_bundles' for related calculators, providing context but not explicit when-not-to-use or 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