Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_valenq_suggest

Read-onlyIdempotent

Ranks candidate emission factors for unstructured invoice, ERP, or BOM descriptions without calculating emissions, helping map activity data to relevant factors.

Instructions

VALENQ Engine Mapping Agent v1 (suggest): Rank candidate emission factors for unstructured invoice, ERP, or BOM descriptions without calculating emissions. Supports source/excludeSource, accessType ('public'|'private'|'all'), regionFallback, effort ('low'|'fast'|'high'|'thorough'), explainResults, PACT DQI, and structured 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>"
    },
    "name": "climeq_valenq_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesRaw invoice, purchase order, or material line description.
unitNoOptional physical unit or ISO currency (e.g., 'kg', 'kWh', 'EUR').
yearNo
limitNo
scopeNo
effortNohigh
regionNoTarget ISO country/region code (e.g., 'TR', 'DE').
sourceNoInclude only this source (mutually exclusive with excludeSource).
unitTypeNoOptional unit family ('Weight', 'Energy', 'Money', etc.).
accessTypeNoall
dataVersionNo
excludeSourceNoSources to exclude (mutually exclusive with source).
explainResultsNo
regionFallbackNoSet false to forbid geographic fallback (default: true).
requiredCategoryNo
sourceLcaActivityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and openWorld, so the bar is lower; the description still adds real value by disclosing that no emissions are computed, that effort levels govern depth, and that results carry PACT DQI plus structured notices[]. Return shape is only loosely characterized, but the key behavioral traits are surfaced.

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?

Front-loaded with the core action and scope boundary, then a compact enumeration of supported options in a single breath. The 'VALENQ Engine Mapping Agent v1' branding and redundant '(suggest)' add little, but overall the text is dense and waste-free.

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 16-parameter tool with no output schema, the description is only partially sufficient: it names many options but leaves roughly half the parameters unexplained and only gestures at the response structure via 'PACT DQI' and 'notices[]'. An agent could invoke it with just text, but would be guessing at filtering parameters.

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 only 44% schema coverage across 16 parameters, the description should carry more weight. It does annotate several high-value options (source vs excludeSource exclusivity, the three accessType values, regionFallback, the effort ladder, explainResults), but leaves text, unit, year, limit, scope, region, unitType, dataVersion, requiredCategory and sourceLcaActivity without added meaning.

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 and resource ('Rank candidate emission factors') plus the input domain (unstructured invoice, ERP, or BOM descriptions) and an explicit scope boundary ('without calculating emissions') that separates it from the climeq_valenq_estimate siblings.

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?

The 'without calculating emissions' clause implies the boundary against calculation tools, and the feature list hints at filter workflows, but no alternative tool is named and no when-to-use/when-not conditions are spelled out. The agent must infer that ranking comes before estimation.

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