Skip to main content
Glama

csrd_esg_calculator

Read-onlyIdempotent

[Deterministic corporate ESG carbon accounting. Pure calculation, read-only, side-effect free]. Calculates official Scope 1 direct emissions and Scope 2 indirect emissions (Location-based & Market-based tCO2e) and standard European VSME / ESRS governance and workforce indicators using ISPRA, DEFRA, and EEA official emission factors. Usage: Use this tool for corporate carbon accounting and CSRD sustainability reporting. For product-level carbon border tariff liabilities on imported raw materials, use 'cbam_embedded_emissions' instead. Returns: JSON object with { scope1_tCO2e: number, scope2_location_tCO2e: number, scope2_market_tCO2e: number, totalEmissions_tCO2e: number, esrsMetrics: { genderPayGap: number, femaleManagerRatio: number, accidentFrequencyRate: number } }.

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": {
      "scope1": "<scope1>",
      "scope2": "<scope2>"
    },
    "name": "csrd_esg_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
scope1YesDirect Scope 1 fuel and refrigerant consumption
scope2YesIndirect Scope 2 purchased electricity consumption
companyMetricsNoWorkforce and governance social indicators for ESRS S1 / G1 disclosures

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description reinforces the safety profile with 'deterministic', 'pure calculation', and 'side-effect free', and discloses which authoritative factor datasets back the numbers. That is genuine context beyond the annotations, though it does not cover edge cases such as missing inputs, unit mismatches, or how unknown country codes 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 definition is front-loaded and cleanly sectioned with bracketed mode summary then 'Usage:' and 'Returns:' labels, so an agent can scan it quickly. Minor redundancy exists in 'Pure calculation, read-only, side-effect free', which partially restates the supplied readOnlyHint, but no sentence is wasted overall.

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?

For a three-parameter nested-object tool with no output schema, the description spells out the return shape field by field (scope1, scope2 location/market, total, esrsMetrics) and names the calculation basis, which is exactly what the missing output schema requires. It stops short of stating input validation or failure behavior, which keeps it from a 5.

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 every nested field (dieselLiters, electricityKwh, renewableSharePercent, countryCode, companyMetrics fields) is already documented in the schema. The description adds the output framing (location vs market-based) but does not explain parameter-level behavior such as the IT default for countryCode or how renewableSharePercent interacts with the market-based figure, so the baseline 3 applies.

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?

The description names a specific verb and resource ('calculates official Scope 1 direct emissions and Scope 2 indirect emissions') and extends it to named ESRS/VSME indicators, with the factor sources (ISPRA, DEFRA, EEA) stated. It also distinguishes itself from the product-level alternative 'cbam_embedded_emissions', so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

There is an explicit 'Usage' line naming the target scenario (corporate carbon accounting, CSRD sustainability reporting) and an explicit exclusion with the substitute tool ('For product-level carbon border tariff liabilities ... use cbam_embedded_emissions instead'). Nothing about when to select or avoid this tool is left to inference.

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