Skip to main content
Glama
tresor4k

macalc

calculate_carbon_footprint

Estimate your annual personal carbon footprint in tonnes of CO₂ equivalent. Input housing, transport, diet, and lifestyle data. Receive total emissions and a detailed breakdown to boost sustainability awareness.

Instructions

Estimate annual personal carbon footprint (tCO₂e). Use for sustainability awareness. Inputs: housing, transport, diet, lifestyle. Returns total emissions and breakdown. See list_bundles for related 'vie-quotidienne' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
km_carNoCar km/year
km_planeNoFlight km/year
kwhNoElectricity kWh/year
meat_kg_weekNoMeat kg/week

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?

No annotations provided, so description carries full burden. It does not disclose assumptions, emission factor sources, regional specificity, or any limitations. For a calculation tool, this is insufficient: the agent needs to know if results are rough estimates or based on specific models.

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?

Three sentences, no filler. Front-loaded with purpose, then use case, then parameter/output summary, and ends with a pointer to related tools. Every sentence serves a clear function.

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 tool has 4 parameters, 100% schema coverage, and an output schema, the description covers the basics but lacks details about calculation methodology, regional adjustments, or what exactly the 'breakdown' includes. It is adequate but leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage with descriptions, so baseline is 3. The description adds value by mapping parameters to categories ('transport', 'diet', 'housing'), improving semantic understanding 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?

The description clearly states the tool estimates annual personal carbon footprint in tCO₂e, provides a use case (sustainability awareness), lists input categories, and describes the output. It also distinguishes from siblings by referencing related calculators via list_bundles.

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 explicitly says 'Use for sustainability awareness' and directs to list_bundles for related tools. While it gives a clear context, it lacks explicit when-not-to-use instructions or alternatives beyond the bundle reference.

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