Epa Emissions

Ghg Emissions By Sector

ghg_emissions_by_sector

Read-onlyIdempotent

Total greenhouse-gas emissions by INDUSTRY SECTOR within a US state (EPA GHGRP) — answers 'which sectors emit the most in '. Sectors: Power Plants, Refineries, Chemicals, Metals, Minerals, Pulp and Paper, Petroleum and Natural Gas Systems, Waste, etc. Returns each sector's total metric tons CO2e and facility count, ranked. State-scoped (pass a state); data lags ~1.5y so the latest full year (~2023) is auto-selected unless year is given.

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	Reporting year (default: latest available, ~2023).
`state`	Yes	US state — 2-letter code ("TX") or full name ("Texas"). Required (state-scoped, not national).
`sector`	No	Optional — filter to one sector by name (e.g. "Power Plants", "Refineries", "Chemicals").

Output Schema

TableJSON Schema

Name	Required	Description
`state`	Yes	State name searched
`sectors`	Yes	Emissions aggregated by industry sector
`facilities`	Yes	Complete facility records
`facility_count`	Yes	Total number of facilities returned

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 29, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "state": "Texas"
-  },
-  {
-    "limit": 30,
-    "sector": "Power Plants",
-    "state": "California"
-  }
-]New value: +[
+  {
+    "state": "Texas"
+  },
+  {
+    "sector": "Power Plants",
+    "state": "California"
+  }
+]

Changed4 schema fields changedJul 9, 2026

removedInput schema / properties / limit

Removed value: -{
-  "description": "Max results (default 20, max 100).",
-  "type": "number"
-}

changedInput schema / properties / sector / description

Previous value: -"Industry type filter (e.g., \"Power Plants\", \"Petroleum and Natural Gas Systems\", \"Chemicals\")."New value: +"Optional — filter to one sector by name (e.g. \"Power Plants\", \"Refineries\", \"Chemicals\")."

changedInput schema / properties / state / description

Previous value: -"Full state name (e.g., \"Texas\")."New value: +"US state — 2-letter code (\"TX\") or full name (\"Texas\"). Required (state-scoped, not national)."

addedInput schema / properties / year

Added value: +{
+  "description": "Reporting year (default: latest available, ~2023).",
+  "type": "number"
+}

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "facilities": {
+      "description": "Complete facility records",
+      "items": {
+        "properties": {
+          "city": {
+            "description": "City location",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "facility_id": {
+            "description": "Facility identifier",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "industry_type": {
+            "description": "Industry classification",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "latitude": {
+            "description": "Geographic latitude",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "longitude": {
+            "description": "Geographic longitude",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Facility name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "state": {
+            "description": "State name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "total_ghg_emissions_mt_co2e": {
+            "description": "Total GHG emissions in metric tons CO2 equivalent",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Reporting year",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "zip": {
+            "description": "ZIP code",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "facility_count": {
+      "description": "Total number of facilities returned",
+      "type": "number"
+    },
+    "sectors": {
+      "description": "Emissions aggregated by industry sector",
+      "items": {
+        "properties": {
+          "facility_count": {
+            "description": "Number of facilities in this sector",
+            "type": "number"
+          },
+          "sector": {
+            "description": "Industry sector name",
+            "type": "string"
+          },
+          "total_emissions_mt_co2e": {
+            "description": "Aggregated emissions for sector in metric tons CO2e",
+            "type": "number"
+          }
+        },
+        "required": [
+          "sector",
+          "facility_count",
+          "total_emissions_mt_co2e"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "state": {
+      "description": "State name searched",
+      "type": "string"
+    }
+  },
+  "required": [
+    "state",
+    "facility_count",
+    "sectors",
+    "facilities"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "state": "Texas"
+  },
+  {
+    "limit": 30,
+    "sector": "Power Plants",
+    "state": "California"
+  }
+]

First observedApr 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds context: data source (EPA GHGRP), data lag (~1.5y), auto-selection of latest year, return fields (metric tons CO2e, facility count). 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with purpose, then details. Every sentence adds value. Could be slightly tighter, but very effective.

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 tool's simplicity (3 params, 1 required, no enums, output schema exists), the description fully covers purpose, inputs, data source, lag, return format, and ranking. No 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?

Schema covers all 3 parameters with descriptions. The description adds value by explaining state accepts 2-letter code or full name, year defaults to latest, and sector is an optional filter. Examples reinforce usage.

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 provides total greenhouse-gas emissions by industry sector within a US state, answering a specific question ('which sectors emit the most in <state>'). It names sectors and distinguishes from facility-level tools (sibling exists).

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 gives clear context on when to use (state-scoped, sector-level emissions) and includes examples. It does not explicitly state when not to use or list alternatives, but the sibling list includes facility-level tools, implying boundary.

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

All Epa Emissions 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.