Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_cloud_carbon

Calculate AWS, Azure, or GCP cloud workload operational (PUE-adjusted) and Scope 3 hardware embodied carbon emissions for reporting.

Instructions

Calculate AWS, Azure, or GCP cloud workload operational (PUE-adjusted) and Scope 3 hardware embodied carbon 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": {
      "provider": "<provider>",
      "region": "<region>"
    },
    "name": "climeq_calculate_cloud_carbon"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYesCloud region (e.g., 'eu-central-1', 'westeurope', 'europe-west1').
persistNo
providerYes
vcpuHoursNo
storageTypeNossd
memoryGbHoursNo
storageGbHoursNo
networkEgressGbNo
includeEmbodiedEmissionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and readOnlyHint=false, so the agent knows this is not a pure read. The description usefully adds that results are PUE-adjusted and include Scope 3 embodied hardware, but it omits the key behavioral detail that a 'persist' input exists which likely writes a record, and says nothing about the external factor data source or result reliability implied by openWorldHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense but front-loaded sentence with no filler, and the provider scope plus the two emission scopes are stated up front. Nothing could be removed without losing information.

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 nine-parameter estimator with no output schema and an 11% schema coverage rate, the description is too thin: it doesn't explain how inputs combine into a result, doesn't mention what is returned, and doesn't disclose the persistence side effect flagged by readOnlyHint=false.

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 only 11% (only 'region' is annotated), yet the description adds almost no parameter meaning: it never explains vcpuHours, memoryGbHours, storageGbHours, networkEgressGb, storageType, or persist, and gives no units or defaults. Only the embodied-emissions toggle is indirectly referenced. With eight undocumented parameters this is a significant gap the description should have filled.

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?

The description gives a specific verb ('Calculate') with a well-scoped resource: AWS/Azure/GCP cloud workload emissions, explicitly splitting operational (PUE-adjusted) from Scope 3 embodied hardware. That is materially more precise than the bare name, though it never contrasts itself with the neighboring climeq_calculate_electricity tool, which an agent might plausibly reach for instead.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the phrase 'cloud workload' alone that this is the right tool versus the electricity, PCF, or classification estimators in the sibling list, and nothing states preconditions such as needing a known region or workload sizing.

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