Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_create_private_factor

Creates a tenant-isolated private emission factor, such as a verified supplier EPD, for immediate use in calculations and the VALENQ Engine.

Instructions

Create a tenant-isolated private emission factor (e.g., verified supplier EPD) usable immediately in calculations and VALENQ Engine (accessType: 'private').

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": {
      "name": "<name>",
      "activityId": "<activityId>",
      "unit": "<unit>",
      "co2eTotal": "<co2eTotal>"
    },
    "name": "climeq_create_private_factor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
unitYes
yearNo
regionNo
sourceNo
categoryNo
co2eTotalYes
activityIdYes
sourceLinkNo
uncertaintyNo
sourceLcaActivityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so safety basics are covered. The description adds meaningful non-annotation context: tenant isolation (scoping of the created record) and immediate availability in calculations and the VALENQ Engine. It still omits duplicate-handling, validation failures, and permissions, which matter for a non-idempotent create.

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 beginning with the verb, with no filler. The parenthetical brand/accessType details are dense but earn their place in a one-line definition.

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 non-idempotent create with 11 undocumented parameters and no output schema, the description is far too thin. It never explains required-field obligations, uniqueness/duplicate behavior, or what the caller receives on success, leaving the agent to guess at most of the invocation contract.

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 11 parameters (4 required), so the description must compensate, and it does not: it names no parameter except the non-parameter accessType. Terms like 'emission factor' and 'supplier EPD' loosely hint at activityId/unit/co2eTotal/source, but an agent gets no guidance on required fields or formats such as year, region, uncertainty, or sourceLcaActivity.

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+resource ('Create a tenant-isolated private emission factor') and qualifies the scope with 'private' / accessType: 'private', which separates it from the public-factor siblings like climeq_search_factors and from climeq_list_private_factors. It doesn't name those siblings directly, so it stops short of full differentiation.

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?

Usage is only implied: the 'verified supplier EPD' example suggests this is for company-specific data not covered by public factor search, and 'usable immediately in calculations' signals intent. There is no explicit when-to-use, when-not-to-use, prerequisite (tenant/auth), or named alternative such as climeq_search_factors for existing factors.

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