Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_commuting

Calculate Scope 3 Category 7 employee commuting and teleworking electricity emissions from workforce commute data, travel modes, remote-work days, and country-specific factors.

Instructions

Calculate Scope 3 Category 7 annual employee commuting and teleworking (work-from-home) electricity emissions.

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": {
      "employeesCount": "<employeesCount>",
      "oneWayCommuteDistanceKm": "<oneWayCommuteDistanceKm>"
    },
    "name": "climeq_calculate_commuting"
  }
}

Input Schema

NameRequiredDescriptionDefault
persistNo
travelModeNocar
countryCodeNoTR
employeesCountYes
fuelOrPowertrainNoaverage
workingDaysPerYearNo
oneWayCommuteDistanceKmYes
remoteWorkingDaysPerYearNo
remoteWorkDailyElectricityKwhNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.8/5.0
Behavior2/5

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

The annotations declare that this is not read-only, is open-world and non-idempotent, but the description does not explain the side effects, whether persist writes a record, or how external emission factors are used. For a calculation tool with a persistence option, key behavioral context is missing.

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?

It is a single front-loaded sentence with no filler or repetition. It is compact, though the compactness leaves important detail unstated for a complex tool.

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?

The tool has nine parameters, 0% schema description coverage, no output schema, and non-read-only/open-world annotations, so the description should carry more explanatory burden. Missing usage guidance, parameter semantics, and behavioral details make it incomplete for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description names none of the nine parameters, including required employeesCount and oneWayCommuteDistanceKm or optional travelMode, fuelOrPowertrain, remoteWorkingDaysPerYear, and persist. It adds no parameter meaning beyond the bare schema.

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?

The description uses a specific verb, 'Calculate', and a precise scope: Scope 3 Category 7 annual employee commuting and teleworking electricity emissions. That domain wording distinguishes it from sibling calculators such as air travel, fuel, freight, and procurement spend.

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?

It gives no when-to-use guidance, prerequisites, exclusions, or alternatives. An agent is not told when to choose this over climeq_calculate_emission, climeq_calculate_electricity, or the other calculation tools.

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