Skip to main content
Glama

NovaPixel LexGrid

csrd_esg_calculator

Calculate official Scope 1 and Scope 2 (Location-based & Market-based tCO2e) emissions and standard European VSME / ESRS indicators using ISPRA, DEFRA and EEA factors.

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
scope1Yes
scope2Yes
companyMetricsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses output units (tCO2e) and factor sources, but does not say whether the tool is read-only, what it returns structurally, how it handles missing optional inputs, or whether calculations are deterministic.

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 description is a single dense sentence with no filler and the core action is front-loaded. It is efficient, though the lack of structure makes it harder to extract the input/output contract.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex calculator with nested inputs, no annotations, and no output schema, so the description needs to do more. It does not explain required inputs, which indicators are produced, or what an agent should expect back, leaving the definition substantially incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported as 0% at the top level, and the description does not explain the three input objects or their required fields. It mentions Scope 1 and Scope 2 but does not mention that companyMetrics exist for diversity and accident indicators, leaving a material gap.

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 states a specific verb ('Calculate') and resource ('Scope 1 and Scope 2 emissions', 'VSME / ESRS indicators'), and names the factor sources (ISPRA, DEFRA, EEA). It is clear enough to distinguish from the financial siblings, though the scope of 'standard European VSME / ESRS indicators' remains somewhat vague.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance, no prerequisites, and no alternatives or exclusions. An agent can infer it is for emissions/ESG calculation, but that is only implied rather than stated.

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