Skip to main content
Glama

scope3_spend_based_eeio_calculator

Read-onlyIdempotent

[Scope 3 spend-based EEIO supply chain carbon screener. Deterministic calculation, read-only, side-effect free]. Estimates Scope 3 Category 1/2 supply chain emissions per euro spent mapped to Eurostat/EXIOBASE NACE Rev. 2 economic sectors, providing CSRD ESRS E1 Tier 3 screening baselines. Usage: Use this tool to quickly calculate carbon intensity from procurement accounting ledgers when primary supplier activity data is unavailable. Returns: JSON object with { spendAmountEur: number, naceSectorCode: string, naceSectorTitle: string, spendEmissionIntensityKgCo2ePerEur: number, calculatedEmissions: object, dataQualityTier: string }.

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": {
      "spendAmountEur": "<spendAmountEur>",
      "naceSectorCode": "<naceSectorCode>"
    },
    "name": "scope3_spend_based_eeio_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
naceSectorCodeYes2-digit or 3-digit NACE Rev. 2 sector code (e.g. J62 Software, C20 Chemicals, C24 Basic Metals, M69 Legal/Accounting)
spendAmountEurYesTotal invoice expenditure or procurement spend in EUR
inflationAdjustmentYearNoYear of expenditure (default: 2024 EUR)
isCapitalExpenditureCapexNoTrue if spend is CapEx (Scope 3 Category 2 Capital goods) rather than OpEx (Category 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description largely restates those ("read-only, side-effect free, deterministic"). The added value is real though: it discloses the underlying data source (Eurostat/EXIOBASE, NACE Rev. 2), the screening-only data quality positioning (Tier 3), and the exact response keys in the absence of an output schema.

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?

Well front-loaded: a bracketed one-line summary, then Usage, then Returns, all in three compact blocks. Minor waste in "Deterministic calculation, read-only, side-effect free," which duplicates the annotations, but nothing else is filler.

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, listing the returned JSON fields is exactly the right compensation, and the four-parameter schema is fully self-documented. What is missing is a note on calculation assumptions or limitations (e.g. sector-average vs. supplier-specific accuracy), which matters for a screening tool feeding CSRD reporting.

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 the schema already explains all four parameters, setting the baseline at 3. The description does add a little meaning by tying Category 1 vs Category 2 to the CapEx/OpEx distinction, but it never mentions the inflationAdjustmentYear parameter or explains how the NACE code granularity affects the mapping.

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: estimates Scope 3 Category 1/2 supply chain emissions per euro spent, mapped to Eurostat/EXIOBASE NACE Rev. 2 sectors. The spend-based EEIO method and CSRD ESRS E1 Tier 3 framing distinguish it from sibling calculators such as cbam_embedded_emissions or business_travel_flight_calculator without needing to name them.

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?

"Use this tool to quickly calculate carbon intensity from procurement accounting ledgers when primary supplier activity data is unavailable" gives a clear triggering condition and implicitly defines the exclusion (use activity-based data when available). It stops short of naming an explicit alternative tool or stating when a spend-based screen is inappropriate, so it falls just below the top band.

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