Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_valenq_estimate

Maps raw ERP, invoice, or BOM descriptions to emission factors, calculates CO2e, and applies CPI adjustment for spend inputs.

Instructions

VALENQ Engine Mapping Agent v1 (estimate): Autonomously map unstructured text to the best emission factor and calculate CO2e emissions, applying currency-aligned compound CPI deflation (applyInflationAdjustment) for monetary inputs and returning PACT DQI, uncertaintyRangeKg, top1Explanation, and notices[].

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

Input Schema

NameRequiredDescriptionDefault
textYesRaw ERP, invoice, or BOM line item description.
unitYesPhysical unit ('kg', 't', 'kWh', 'L') or currency ('EUR', 'USD', 'TRY').
yearNo
amountYes
effortNohigh
regionNo
sourceNo
persistNo
accessTypeNoall
dataVersionNo
excludeSourceNo
explainResultsNo
regionFallbackNo
externalReferenceIdNo
applyInflationAdjustmentNoSpend year (e.g., 2026) for compound CPI inflation adjustment on monetary inputs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.8/5.0
Behavior3/5

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

The description adds genuine behavioral context beyond the annotations: currency-aligned compound CPI deflation for monetary inputs and the exact return payload (PACT DQI, uncertaintyRangeKg, top1Explanation, notices[]), which matters because there is no output schema. However, annotations declare readOnlyHint=false and idempotentHint=false, and the description never explains the write side effect — presumably the persist parameter — so an agent cannot tell when state is mutated.

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

Conciseness3/5

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

The definition is a single dense sentence, so it is compact and front-loads the core action. But it is jargon-heavy ('VALENQ Engine Mapping Agent v1', 'PACT DQI') and spends its limited space on return-field names while omitting higher-value parameter and side-effect information.

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?

For a 15-parameter tool with 20% schema coverage, no output schema, and non-read-only annotations, the description is under-specified. Listing the return fields is helpful compensation for the missing output schema, but the semantics of effort levels, region fallback behavior, source filtering, and the persist side effect are all absent, leaving real risk of incorrect invocation.

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 only 20% across 15 parameters, so the description carries a heavy burden and mostly fails it. It explains only applyInflationAdjustment, and even that explanation duplicates the schema's own description. Critical parameters such as effort (fast/low/thorough/high), accessType, regionFallback, excludeSource, persist, and dataVersion are left completely undefined in both places.

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: autonomously map unstructured text to an emission factor and calculate CO2e. That distinguishes it reasonably from calculation siblings like climeq_calculate_electricity, but it never explicitly contrasts with climeq_valenq_suggest or climeq_valenq_estimate_batch, so the differentiation is implied rather than stated.

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 when-to-use or when-not-to-use guidance. The description never says why an agent should pick this over climeq_valenq_suggest (which presumably just suggests factors), the batch variant, or the per-category calculate_* tools. The only routing signal is the word 'estimate' in the name.

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