Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_valenq_estimate_batch

Read-onlyIdempotent

Maps and calculates GHG emissions for up to 100 unstructured ERP/BOM line items in one request, enabling batch estimation from messy inventory data.

Instructions

VALENQ Engine Batch Mapping & Estimation: Autonomously map and calculate GHG emissions for up to 100 unstructured ERP/BOM line items in a single request.

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": {
      "items": "<items>"
    },
    "name": "climeq_valenq_estimate_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
dataVersionNo
includeOpenLcaPackageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description's "autonomously map" adds meaningful context about LLM-driven mapping in an open world, but it does not disclose what happens to unmappable lines, whether partial results are returned, or any limits on failures within a 100-item request.

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 with no filler, and the batch limit is placed early where it matters. The "VALENQ Engine Batch Mapping & Estimation:" prefix partially restates the tool name and the rest of the sentence, costing some density.

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 complex batch-mapping tool with a nested item schema, no output schema, and zero parameter documentation, the description leaves the agent unable to predict the response shape or per-line failure behavior. Given there is no output schema to fall back on, the description should explain what mapping results and identifiers come back.

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 coverage is 0% and the description explains almost none of the parameters. It conveys that items are line items and that the batch cap is 100, but says nothing about the required nested fields (text, amount, unit), the optional year/region/category/lineId, or what dataVersion and includeOpenLcaPackage control.

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 pair ("map and calculate") and resource ("GHG emissions") with an explicit scope constraint ("up to 100 unstructured ERP/BOM line items in a single request"). This implicitly separates it from the single-item sibling climeq_valenq_estimate via the word "batch", but no sibling is named or contrasted directly.

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

Usage Guidelines3/5

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

Usage is only implied: the mention of "up to 100" line items and "batch" in the name signals when this tool is preferred over a one-at-a-time estimate, but there is no explicit when-to-use, when-not-to-use, or named alternative such as climeq_valenq_estimate.

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