Skip to main content
Glama

ispra_grid_electricity_factor

Read-onlyIdempotent

[ISPRA & AIB European electricity emission factor resolver. Deterministic calculation, read-only, side-effect free]. Calculates Scope 2 electricity emissions across EU-27 member states using certified ISPRA, EEA, and AIB Residual Mix factors, comparing location-based and market-based accounting with Guarantees of Origin (GOs). Usage: Use this tool to calculate Scope 2 emissions for CSRD ESRS E1 reporting and ISO 14064 GHG inventories. Returns: JSON object with { countryIso2: string, accountingMethod: string, consumptionKwh: number, emissionFactorGco2ePerKwh: number, calculatedEmissions: object, esrsE1DisclosureMapping: 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": {
      "consumptionKwh": "<consumptionKwh>",
      "countryIso2": "<countryIso2>"
    },
    "name": "ispra_grid_electricity_factor"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryIso2Yes2-letter ISO country code (e.g. IT, DE, FR, ES, PL)
reportingYearNoReporting year (e.g. 2024, 2025, 2026)
consumptionKwhYesElectricity consumption in kilowatt-hours (kWh)
accountingMethodNoGHG Protocol Scope 2 accounting method (default: LOCATION_BASED)
hasGuaranteesOfOriginGoNoTrue if electricity is covered by certified Guarantees of Origin (grants 0 gCO2e/kWh in market-based)

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?

Annotations already declare readOnlyHint and idempotentHint, and the bracketed preamble ('deterministic calculation, read-only, side-effect free') largely restates them. What the description genuinely adds is data provenance (certified ISPRA/EEA/AIB Residual Mix factors) and the declared return shape. It does not cover edge behavior such as unsupported country codes or how reportingYear affects factor vintage, which is the remaining behavioral gap.

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 labeled structure (bracket preamble, Usage, Returns) is front-loaded and easy to scan, and the Returns line is genuinely useful given there is no output schema. Minor waste exists in 'read-only, side-effect free', which duplicates the annotations.

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 compensates by enumerating the return object's fields, and usage plus factor provenance cover the core decision. It is nearly complete for a single deterministic calculator; only edge-case behavior (invalid/unsupported country, year handling) is unaddressed.

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 all five parameters including the accountingMethod enum and the Guarantees of Origin flag are already documented in structured form. The description only reiterates that location-based and market-based are compared; it adds no syntax, default, or constraint detail beyond the schema. Baseline 3 is appropriate.

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 names a specific verb and resource with explicit scope: calculating Scope 2 electricity emissions across EU-27 using ISPRA, EEA, and AIB Residual Mix factors, with location-based vs market-based comparison. An agent knows exactly what computation is performed. It stops short of naming a sibling (e.g. esg_ghg_emission_factor_resolver) to disambiguate against, so a 4 rather than 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' line gives clear positive context: CSRD ESRS E1 reporting and ISO 14064 GHG inventories. That is enough to route most requests correctly. There are no explicit exclusions (e.g. non-EU consumption, non-electricity Scope 1/3 emissions) and no named alternative tool, so it falls short of a 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