Skip to main content
Glama

esg_ghg_emission_factor_resolver

Read-onlyIdempotent

[Deterministic ESG GHG emission factor resolver. Pure calculation, read-only, side-effect free]. Resolves statutory emission factors from official ISPRA, DEFRA, and EEA databases for Scope 1 (fuel combustion), Scope 2 (electricity market/location-based), and Scope 3 (business travel, freight, cloud data centers) activities, mapping output to CSRD ESRS E1 reporting standards. Usage: Use this tool to convert corporate activity data (kWh, Smc, Liters, pkm, tkm) into certified metric tonnes of CO2 equivalent (tCO2e). Returns: JSON object with { activityQuantity: number, unit: string, emissionFactorKgCo2ePerUnit: number, databaseSource: string, totalEmissionsKgCo2e: number, totalEmissionsTco2e: number, esrsE1Classification: object }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "activityCategory": "<activityCategory>",
      "activityAmountUnits": "<activityAmountUnits>"
    },
    "name": "esg_ghg_emission_factor_resolver"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryCodeNoGeographic jurisdiction for emission factor resolution (default: IT)
reportingYearNoTarget reporting fiscal year (default: 2024)
activityCategoryYesOperational emission activity category
activityAmountUnitsYesNumeric volume of activity consumed (Smc, Liters, kWh, pkm, tkm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, and the description largely restates this as 'pure calculation, read-only, side-effect free'. It does add real behavioral context by naming the factor provenance (statutory ISPRA/DEFRA/EEA databases) and the determinism guarantee, which an agent cannot infer from the schema. It says nothing about failure modes, unsupported units, or coverage limits of the enums, so it remains a middling disclosure above an already-covered safety profile.

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 definition is short, front-loaded with a bracketed one-line characterization, then explicit 'Usage' and 'Returns' sections, which is easy to scan. Minor waste in the bracketed preamble duplicating the read-only annotations, but no sentence is seriously off-topic.

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

Completeness4/5

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

With no output schema, the description usefully spells out the return object fields (activityQuantity, emissionFactorKgCo2ePerUnit, databaseSource, totalEmissionsKgCo2e/Tco2e, esrsE1Classification), which is the key gap it needed to fill. Combined with full schema coverage and safety annotations, an agent has what it needs to call the tool; only error and unsupported-input behavior is missing.

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%, including enum docs and defaults, so the schema already carries the parameter burden and 3 is the baseline. The description adds only marginal meaning, repeating the unit set (kWh, Smc, Liters, pkm, tkm) and mapping categories to Scope 1/2/3, but it does not explain how countryCode or reportingYear affect factor selection.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb and resource: it 'resolves statutory emission factors' from named official databases (ISPRA, DEFRA, EEA) across Scope 1/2/3 activity types, and maps output to CSRD ESRS E1. That is far more specific than a restated name. It stops short of distinguishing itself from overlapping siblings such as ispra_grid_electricity_factor, defra_freight_logistics_calculator, or csrd_esg_calculator, so it does not earn a 5.

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 'Usage' sentence gives an explicit trigger: convert corporate activity data in kWh/Smc/Liters/pkm/tkm into tCO2e. An agent can tell from this when the tool applies. There is no when-not guidance and no named alternative for cases that fall outside its activity enums, which keeps it below 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources