Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_pcf

Calculate ISO 14067/WBCSD PACT product carbon footprints from a bill of materials, scrap rates, recycled content, and manufacturing energy for cradle-to-gate or cradle-to-grave assessments.

Instructions

Calculate ISO 14067 / WBCSD PACT Product Carbon Footprint (Cradle-to-Gate or Cradle-to-Grave) from a Bill of Materials (BOM), scrap rates, recycled content, and manufacturing energy.

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": {
      "productName": "<productName>",
      "components": "<components>"
    },
    "name": "climeq_calculate_pcf"
  }
}

Input Schema

NameRequiredDescriptionDefault
componentsYes
productNameYes
boundaryTypeNoCradleToGate
manufacturingNo
referenceFlowUnitNounit
primaryRegionOfUseNo
referenceFlowAmountNo
persistProductImpactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already disclose readOnly=false, idempotent=false and openWorld=true, so the safety bar is lower, and the description usefully adds methodology context (standards, cradle-to-gate vs cradle-to-grave). However, it never mentions the persistProductImpact capability implied by the schema, leaving the agent unaware that a calculation can be written/persisted and that repeat calls are non-idempotent and could duplicate records.

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 verb and resource; the parenthetical boundary list and input enumeration are dense but non-redundant. No filler or marketing language.

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 an 8-parameter tool with nested objects, no output schema and no parameter documentation, the description gives enough to understand the domain model but not enough to call it confidently — units, reference-flow semantics and the persistence side effect are all undisclosed. Since no output schema exists, the return-value omission is forgivable, but the persistence gap is not.

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 0% across 8 parameters, including a nested components array, so the description carries the full explanatory burden. It maps roughly half the fields by naming BOM, scrap rates, recycled content, manufacturing energy and boundary type, but says nothing about productName, weightKg units, region, referenceFlowUnit/referenceFlowAmount, gridZone/fuelKg, or the persistProductImpact flag.

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?

Names a specific verb and resource ('Calculate Product Carbon Footprint') and pins it to ISO 14067 / WBCSD PACT plus the two boundary types, so the operation is unmistakable. It never contrasts itself with the sibling screening tool (climeq_screen_pcf_ai), which is the main ambiguity given both concern PCFs.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The only implied usage comes from the enumerated inputs (BOM, scrap, recycled content), so an agent must infer that this is the detailed bottom-up calculation path rather than the AI screening path.

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