Skip to main content
Glama

defra_freight_logistics_calculator

Read-onlyIdempotent

[DEFRA & GLEC freight logistics carbon engine. Deterministic calculation, read-only, side-effect free]. Calculates Scope 3 Category 4/9 freight transport emissions across road HGV (Euro 4-6), rail (electric/diesel), maritime, and air cargo based on ISO 14083:2023 and GLEC Framework v3.0, reporting Tank-to-Wheel (TTW) and Well-to-Wheel (WTW) emissions. Usage: Use this tool to calculate logistics and supply chain transportation carbon footprints per tonne-kilometre (t*km). Returns: JSON object with { cargoWeightMetricTons: number, distanceKm: number, transportMode: string, tonneKilometres: number, emissionFactors: object, calculatedTotals: object, glecFrameworkAlignment: 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": {
      "cargoWeightMetricTons": "<cargoWeightMetricTons>",
      "distanceKm": "<distanceKm>",
      "transportMode": "<transportMode>"
    },
    "name": "defra_freight_logistics_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
distanceKmYesOne-way transport distance in kilometres
transportModeYesFreight transportation mode
cargoWeightMetricTonsYesWeight of cargo in metric tonnes
emptyRunningFactorPercentNoEmpty return trip allocation percentage (default: 15%)
isRefrigeratedTemperatureControlledNoTrue if cargo requires active temperature-controlled refrigeration (+18% fuel penalty)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and idempotentHint, so the safety profile is known. The description adds useful behavior beyond that: a deterministic, side-effect-free engine, reporting both Tank-to-Wheel and Well-to-Wheel figures, and an explicit return-field list including glecFrameworkAlignment. It stops short of noting limits such as supported value ranges or rounding conventions.

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?

Front-loaded with the core purpose, then cleanly labeled 'Usage' and 'Returns' sections. The bracketed preamble restates annotations already provided, which is mild redundancy, but no sentence is padding.

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 returned JSON fields, which is exactly what the agent needs. It omits edge-case behavior such as unit validation or how unsupported mode/distance combinations are handled, a minor gap for a deterministic calculator.

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%, and the schema already explains each parameter including the empty-running default of 15% and the +18% refrigeration penalty, so the baseline is 3. The description adds domain framing (tonne-kilometres, TTW/WTW, framework alignment) but no per-parameter meaning beyond the schema.

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?

States a specific verb and resource ('Calculates Scope 3 Category 4/9 freight transport emissions') plus the supported modes (road HGV Euro 4-6, rail electric/diesel, maritime, air) and standards (ISO 14083:2023, GLEC v3.0). This cleanly separates it from spend-based siblings such as scope3_spend_based_eeio_calculator, which cannot do per-tonne-kilometre mode-specific calculation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Usage' line tells the agent to use it for logistics/supply chain footprints per tonne-kilometre, which is clear positive guidance. However, there is no exclusion or boundary statement—nothing says when to prefer a spend-based or business-travel calculator instead, so the agent must infer the split.

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