Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_estimate_by_classification

Calculate physical or spend-based GHG emissions from UNSPSC, NAICS, ISIC, NACE, MCC, or HS_CODE classification codes to support carbon accounting and reporting.

Instructions

Calculate physical or spend-based GHG emissions from standard industry/customs taxonomy codes (UNSPSC, NAICS, ISIC, NACE, MCC, HS_CODE).

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": {
      "classificationType": "<classificationType>",
      "classificationCode": "<classificationCode>",
      "amount": "<amount>",
      "unitOrCurrency": "<unitOrCurrency>"
    },
    "name": "climeq_estimate_by_classification"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo
amountYes
persistNo
regionCodeNo
unitOrCurrencyYes
classificationCodeYes
classificationTypeYes

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=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is partly covered. The description adds the physical vs. spend-based mode distinction but says nothing about the `persist` flag writing an estimate to storage, whether calculations are deterministic, or what external factor data the open-world call reaches — the key behavioral facts for a non-readonly tool.

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; the verb and resource come first and the parenthetical enum scan is compact. It is appropriately sized for what it says, though it is under-specified rather than over-specified.

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 7-parameter, 4-required tool with zero schema descriptions, a possible write via `persist`, and no output schema, the one-sentence description leaves most of the calling contract undocumented. An agent cannot tell what `amount`, `unitOrCurrency`, or `year` expect, nor what the calculation returns.

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, so the description carries the full burden and mostly fails it. It restates the classificationType enum already in the schema and gestures at unitOrCurrency via 'physical or spend-based', but never explains amount, year, regionCode, or the side-effecting `persist` parameter.

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?

Names a specific verb (Calculate) and resource (GHG emissions) plus the distinctive input family (industry/customs taxonomy codes with the six enum values). This differentiates it from siblings like climeq_calculate_electricity or climeq_calculate_procurement_spend, though it never names an alternative explicitly.

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 agent can infer this is the tool for emissions estimates keyed by classification code, and 'physical or spend-based' hints at two modes. There is no statement of when to prefer it over climeq_calculate_procurement_spend or climeq_calculate_emission, nor any prerequisites or exclusions.

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