Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_emission

Calculates Scope 1–3 greenhouse gas emissions from activity amount and unit using emission factors, with region/year fallback and optional ledger or blockchain anchoring.

Instructions

Core ClimeqAI GHG calculation engine supporting deterministic emissionFactorId/activityCode, strict regionFallback/yearFallback, custom tenant rules, optional ledger persistence (persist), and SHA-256 anchorToBlockchain.

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": {
      "amount": "<amount>",
      "unit": "<unit>"
    },
    "name": "climeq_calculate_emission"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
yearNo
scopeNo
amountYes
regionNo
persistNo
dataVersionNo
descriptionNo
activityCodeNo
yearFallbackNo
regionFallbackNo
emissionFactorIdNo
calculationMethodNoar6
anchorToBlockchainNo
externalReferenceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Adds meaningful behavior beyond annotations: it discloses that resolution is deterministic via emissionFactorId/activityCode, that region/year fallbacks can be strict, that tenant rules apply, and that persist/anchorToBlockchain are optional side effects writing to a ledger and blockchain. This goes well past the annotations' generic write flags and clarifies the mutation surface.

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?

A single front-loaded sentence that leads with the core purpose and then enumerates capabilities without filler. It is dense with jargon but every clause carries information, so it is efficient though slightly hard to parse.

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

Completeness3/5

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

For a 15-parameter mutation-capable engine with no output schema, the description covers the side-effect surface and factor-resolution logic well, but leaves roughly half the parameters undocumented and gives no guidance on choosing calculationMethod or dataVersion, so it is only partially complete.

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?

With 15 parameters and 0% schema description coverage, the description must carry the burden, and it only explains a minority: emissionFactorId, activityCode, regionFallback, yearFallback, persist, anchorToBlockchain. Critical inputs like unit, amount, scope, region, calculationMethod, and dataVersion remain undefined in both schema and description, so the coverage gap is only partially closed.

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?

States a specific verb and resource: a GHG emission calculation engine, with the notable capabilities it supports (deterministic factor resolution, fallback, persistence, blockchain anchoring). It is clearly a general-purpose calculator, but it never distinguishes itself from sibling calculators like climeq_calculate_electricity or climeq_calculate_fuel, so an agent cannot tell when the generic engine is preferred over a specialized one.

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?

No when-to-use guidance is given. The word 'Core' hints this is the general engine, but there is no explicit statement of when to call it versus the many category-specific sibling calculators, nor any prerequisite or exclusion conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.