Climatiq

Search Factors

search_factors

Read-onlyIdempotent

Search Climatiq's emission-factor database. Use to discover factor IDs and required parameters before calling estimate_emissions. Filter by query, category, source (e.g., "EPA", "DEFRA"), region (ISO code), or year.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "electricity grid",
      "region": "US",
      "category": "electricity",
      "results_per_page": 25
    },
    "name": "search_factors"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based page (default 1)
`year`	No	Publication year
`query`	No	Free-text search (e.g., "electricity grid", "concrete production")
`region`	No	ISO-3166 region code (e.g., "US", "GB", "DE")
`source`	No	Source dataset (e.g., "EPA", "DEFRA", "BEIS", "ecoinvent")
`category`	No	Climatiq category (e.g., "electricity", "fuel", "freight", "computing")
`unit_type`	No	Activity unit type (Energy, Volume, Distance, Mass, etc.)
`results_per_page`	No	1-100 (default 25)

Output Schema

Name	Required	Description
`page`	Yes	Current page number
`results`	Yes	Array of emission factor records
`returned`	Yes	Number of results returned in this response
`total_pages`	Yes	Total number of pages available
`total_results`	Yes	Total number of matching results

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "category": "electricity",
+    "query": "electricity grid",
+    "region": "US",
+    "results_per_page": 25
+  },
+  {
+    "query": "concrete production",
+    "source": "ecoinvent",
+    "unit_type": "Mass",
+    "year": 2023
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "page": {
+      "description": "Current page number",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "results": {
+      "description": "Array of emission factor records",
+      "items": {
+        "properties": {
+          "access_type": {
+            "description": "Access level of the factor",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "activity_id": {
+            "description": "Climatiq activity identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "category": {
+            "description": "Factor category",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Factor ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "lca_activity": {
+            "description": "LCA activity reference",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Factor name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "region": {
+            "description": "ISO region code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "region_name": {
+            "description": "Human-readable region name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sector": {
+            "description": "Industry sector",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source": {
+            "description": "Data source (e.g., EPA, DEFRA)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "unit_type": {
+            "description": "Activity unit type (Energy, Volume, etc.)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Publication year",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of results returned in this response",
+      "type": "number"
+    },
+    "total_pages": {
+      "description": "Total number of pages available",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "total_results": {
+      "description": "Total number of matching results",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "page",
+    "total_pages",
+    "total_results",
+    "returned",
+    "results"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations provide readOnlyHint, idempotentHint, and destructiveHint=false. The description adds workflow context (discovery before estimation) and filtering dimensions, which complements the annotations without contradiction.

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 sentences covering purpose, usage, and filters with no unnecessary words. Front-loaded and efficient.

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?

Given the output schema exists, parameter coverage is high, and annotations are present, the description adequately explains the tool's role and available filters.

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 lists filters and provides examples (e.g., 'EPA', 'DEFRA', ISO code), adding slight nuance but not significantly 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 tool searches Climatiq's emission-factor database to discover factor IDs and required parameters before calling estimate_emissions, distinguishing it from sibling tools like estimate_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?

The description says 'Use to discover factor IDs and required parameters before calling estimate_emissions', implying when to use it. It does not explicitly mention when not to use it or alternatives, but the sibling tool list clarifies the context.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.