Skip to main content
Glama

scope1_stationary_combustion

Read-onlyIdempotent

[Scope 1 stationary fuel combustion & biogenic split auditor. Deterministic calculation, read-only, side-effect free]. Computes Scope 1 direct emissions from stationary fuel combustion (natural gas Sm3, diesel liters, LPG kg, fuel oil kg, wood pellets kg) ex IPCC 2006/2019 guidelines, separating fossil and biogenic CO2 for CSRD ESRS E1. Usage: Use this tool to compute fossil and biogenic emissions from corporate heating boilers, power generators, and industrial furnaces. Returns: JSON object with { fuelType: string, quantityInput: number, netCalorificValueGj: number, emissionFactors: object, calculatedTotals: object, esrsE1Disclosure: 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": {
      "fuelType": "<fuelType>",
      "fuelQuantity": "<fuelQuantity>"
    },
    "name": "scope1_stationary_combustion"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelTypeYesType of stationary fuel consumed
fuelQuantityYesQuantity of fuel consumed in physical units (Sm3 for Gas, Liters for Diesel, Kg for LPG/Oil/Pellets)
biogenicFractionPercentNoPercentage of fuel derived from biogenic/renewable sources (e.g. biomethane mix)

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 bracketed preamble ('deterministic calculation, read-only, side-effect free') largely restates those hints rather than adding new behavior. Genuinely additive details are the IPCC 2006/2019 methodology and the fossil/biogenic split for CSRD ESRS E1, but the description says nothing about which emission-factor set or version is applied or how out-of-range quantities are handled.

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 three-part structure (bracketed trait tag, Usage, Returns) is easy to scan and front-loads the core computation before the guidance. There is mild waste in the trait tag restating the readOnly hint, but overall every sentence carries information an agent can act on.

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 present, the description usefully enumerates the returned JSON fields, covering the return-value gap, and the methodology reference supplies the regulatory framing an auditor needs. It falls short only on emission-factor provenance/versioning and on the optional biogenic parameter, which is the one input left unaddressed in prose.

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 coverage is 100%, so all three parameters, including the unit conventions for fuelQuantity and the fuelType enum, are already documented in the schema. The description repeats the fuel-unit list without adding meaning, and it never mentions biogenicFractionPercent or how it interacts with the fossil/biogenic split, so it adds little beyond the structured data. Baseline 3 applies.

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 gives a specific verb and resource ('Computes Scope 1 direct emissions from stationary fuel combustion') and enumerates the supported fuels with their physical units, so the agent knows exactly what calculation is performed. The 'stationary' qualifier plus the boiler/generator/furnace scope implicitly separates it from mobile-combustion calculators in the catalog, but no sibling is ever named, so differentiation is inferential rather than explicit.

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?

An explicit Usage line names the equipment classes in scope (corporate heating boilers, power generators, industrial furnaces), which is enough for an agent to recognize a qualifying request. There is no when-not guidance and no routing to adjacent tools (e.g., for mobile/freight or travel emissions), which keeps it 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