Skip to main content
Glama
akkapur

energy-emissions-mcp

by akkapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_facility_emissionsA

Get greenhouse gas emissions for large industrial facilities in a US state or county, from the EPA Greenhouse Gas Reporting Program (GHGRP).

Use this for questions like "what are the biggest emitters in Harris
County, TX?" or "total reported facility emissions in Ohio in 2022".
Results are sorted largest emitter first.

Do not use this for a place's total emissions footprint: GHGRP covers only
facilities emitting over 25,000 tonnes CO2e a year (power plants,
refineries, factories, landfills), not homes, vehicles or small businesses.

Args:
    state: Two-letter state code, e.g. "TX".
    county: Optional county name, e.g. "Harris" or "Orleans Parish". Leave
        empty for the whole state.
    year: Reporting year, 2010 to 2023. Defaults to 2023, the latest.
    limit: Maximum facilities to list, 1 to 100. Totals always cover every
        matching facility, even those beyond the limit.

Returns totals in metric tons of CO2-equivalent (direct emissions, excluding
biogenic CO2 and fuel suppliers, matching GHGRP's own facility totals),
plus the source and query URL to cite.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of misselection between tools. Its description also clearly delimits scope (GHGRP facility-level emitters, not a place's total emissions footprint), preventing misuse.

Naming Consistency4/5

The single name `get_facility_emissions` follows a clean verb_noun snake_case convention that would scale predictably. With only one tool there is no cross-tool consistency to verify, so it falls short of a perfect score.

Tool Count2/5

One tool is very thin for a whole emissions data server; there is no way to discover valid states/counties/years or drill into a specific facility. The single endpoint is well-scoped for its narrow query, but the surface is minimal for the apparent domain.

Completeness3/5

The core query (facility emissions by state/county/year) is well covered, including sorting, limits, totals, and citation metadata. However, notable gaps remain: no discovery of valid states/counties/years, no facility-level detail lookup, and no comparison or trend operations.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources