Skip to main content
Glama
SOMA AI Emission Factors (SAEF)

SOMA AI Emission Factors (SAEF)

estimate_chat_usage

Estimate carbon, energy, and water use for chat exchanges from message counts, model, and region using SAEF emission factors for AI sustainability reporting.

Instructions

Estimate carbon, energy and water for chat usage, counted in messages, using SOMA AI Emission Factors (SAEF).

Each message is one chat exchange (a question and its answer) of 1,210 tokens, the dataset's short-chat default of 928 input and 282 output tokens. Long documents, coding agents and reasoning modes use far more tokens, so use estimate_footprint when you know the token count.

Args: messages: Number of chat exchanges. model: Model identifier such as "gpt-4o" or "claude-sonnet-4-5". region: Cloud region id, ISO-3 country code, eGRID subregion, "eu-27" or "global". Use list_regions to see options.

Same output as estimate_footprint, plus the token assumption used. All figures are estimates, not measurements.

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": {
      "messages": "<messages>",
      "model": "<model>"
    },
    "name": "estimate_chat_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
regionNoglobal
messagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the critical computational assumption (1,210 tokens per exchange, split 928 input / 282 output) plus the accuracy caveat that all figures are estimates, not measurements. It also states the output relationship to estimate_footprint. It stops short of stating side effects, permissions, or whether the call is purely read-only, which is the remaining gap for an unannotated tool.

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?

The definition is front-loaded with the purpose and the token assumption that governs the result, then the alternative-tool routing, then a compact Args block. Every sentence adds information an agent needs; nothing is restated from the schema titles without added meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter estimation tool with no output schema and no annotations, the description supplies the assumption model, the accuracy caveat, the output relationship to a sibling, and full parameter meaning. An agent can call it and interpret the result without further context.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate entirely, and it does: messages is defined as the number of chat exchanges, model is given concrete identifier examples, and region enumerates accepted formats (cloud region id, ISO-3 code, eGRID subregion, "eu-27", "global") plus a pointer to list_regions. The default of "global" is visible in schema, and every parameter now has usable 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?

The description names a specific verb and resource: estimate carbon, energy and water for chat usage counted in messages, using a named factor set (SAEF). It also distinguishes itself from the sibling estimate_footprint by scope (message-counted chat exchanges vs. known token counts), so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule: use this tool when working in messages, and switch to estimate_footprint when the token count is known, with the reason (long documents, coding agents, reasoning modes use far more tokens). It also points to list_regions for valid region values, covering the third parameter's selection.

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