Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_screen_pcf_ai

Read-onlyIdempotent

Estimate product mass composition and cradle-to-gate CO2e for product carbon footprint screening when no bill of materials is available.

Instructions

AI BOM-less Product Carbon Footprint screening: Estimate product mass composition and Cradle-to-Gate CO2e when no Bill of Materials is available.

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>"
    },
    "name": "climeq_screen_pcf_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNameYes
totalWeightKgNo
transportModeNo
hsOrUnspscCodeNo
productCategoryNo
destinationRegionNo
manufacturingRegionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds the meaningful behavioral point that this is an AI-based *screening* estimate rather than a factor-based calculation, but it gives no indication of fidelity/uncertainty, what happens when optional inputs like weight or region are omitted, or whether results are persisted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence naming the method, the resource, and the applicability condition, with no filler. Every clause earns its place.

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?

There is no output schema and 7 fully undocumented parameters, so the description carries the burden it does not meet: it never explains the inputs or what the returned estimate looks like (units, breakdown, confidence). For a screening estimator whose accuracy depends heavily on optional inputs, this is a substantial gap.

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 7 parameters, and the description says nothing about any of them — not what totalWeightKg drives, not how transportMode or destinationRegion/manufacturingRegion affect the footprint, and not what hsOrUnspscCode or productCategory are used for. With only productName required, an agent has no way to judge which optional inputs materially change the result.

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 ('Estimate'), specific outputs ('product mass composition and Cradle-to-Gate CO2e'), and a precise scope condition ('when no Bill of Materials is available'). That condition alone lets an agent distinguish it from the BOM-based calculation siblings such as climeq_calculate_pcf without opening any schema.

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?

The trigger condition is explicit: use this when no Bill of Materials exists. It does not name an alternative tool or state an exclusion for cases where a BOM *is* available, so the agent must infer that sibling calculation tools take over then.

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