Climatiq

Estimate Emissions

estimate_emissions

Read-onlyIdempotent

Calculate kgCO₂e for an activity. Pass an emission_factor with at minimum activity_id (from search_factors) or id, plus the required parameters (e.g., { energy: 200, energy_unit: "kWh" }). Returns CO₂e + breakdown.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`parameters`	Yes	Activity quantities matching the factor's required unit type (e.g., {energy:200, energy_unit:"kWh"}).
`emission_factor`	Yes	Selector object — at minimum {activity_id: "..."} or {id: "..."}. May add region, year, source for disambiguation.

Output Schema

TableJSON Schema

Name	Required	Description
`co2e`	Yes	Calculated CO2 equivalent in kg
`co2e_unit`	Yes	Unit of CO2e measurement
`audit_trail`	Yes	Audit trail for the calculation
`activity_data`	Yes	Activity data used in calculation
`emission_factor`	Yes	The resolved emission factor used
`constituent_gases`	Yes	Breakdown of constituent greenhouse gases
`calculation_method`	Yes	Method used for calculation
`calculation_origin`	Yes	Origin/source of the calculation

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "emission_factor": {
+      "activity_id": "electricity-supply_grid_mix-2023"
+    },
+    "parameters": {
+      "energy": 150,
+      "energy_unit": "kWh"
+    }
+  },
+  {
+    "emission_factor": {
+      "id": "9dc73201-e21b-45e3-a033-daac504400c3",
+      "region": "GB"
+    },
+    "parameters": {
+      "mass": 500,
+      "mass_unit": "kg"
+    }
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "activity_data": {
+      "description": "Activity data used in calculation",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "audit_trail": {
+      "description": "Audit trail for the calculation",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "calculation_method": {
+      "description": "Method used for calculation",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "calculation_origin": {
+      "description": "Origin/source of the calculation",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "co2e": {
+      "description": "Calculated CO2 equivalent in kg",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "co2e_unit": {
+      "description": "Unit of CO2e measurement",
+      "type": "string"
+    },
+    "constituent_gases": {
+      "description": "Breakdown of constituent greenhouse gases",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "emission_factor": {
+      "description": "The resolved emission factor used",
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "co2e",
+    "co2e_unit",
+    "calculation_method",
+    "calculation_origin",
+    "emission_factor",
+    "constituent_gases",
+    "activity_data",
+    "audit_trail"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds that it returns CO₂e plus a breakdown, which is transparent about the output. No contradictions.

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 the purpose, second explains the required inputs and output. Every word adds value, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete for a calculation tool with output schema. It mentions return value ('CO₂e + breakdown'), references the prerequisite sibling tool (search_factors), and provides adequate guidance.

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?

Schema description coverage is 100%, but the description adds valuable context with an example (energy:200, energy_unit:'kWh') and clarifies the minimum requirements for emission_factor (activity_id or id), which goes beyond the 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 verb 'Calculate kgCO₂e' for an 'activity', specifying the exact metric and distinguishing it from sibling tools like search_factors which find factors rather than compute emissions.

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?

It explicitly requires an emission_factor from search_factors and parameters, providing an example. However, it does not explicitly state when not to use this tool or suggest alternatives beyond the implicit prerequisite.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Climatiq tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.