Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Calculate Scope 2 emissions

environmental-intelligence_scope-2-emissions-calculate

Calculate Scope 2 emissions from electricity activities and caller factors, disclosed public-style grid factors, or optional key-free Carbon Intensity API intensity. Price $0.04 USDC. POST /api/v1/environmental-intelligence/scope-2-emissions-calculate. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "environmental-intelligence_scope-2-emissions-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
factorsNo
permitsNo
reportsNo
suppliersNo
activitiesNo
waterRecordsNo
waterAnomalyZNo
wasteManifestsNo
carbonIntensityNo
expiryWarningDaysNo
consistencyToleranceKgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful behavior: the $0.04 USDC price, the POST route, and that unpaid calls return 402 without executing. It says nothing about which of the 17 fields must be populated for a valid calculation, what validation failures look like, or what the response contains.

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?

Four tight sentences with the purpose front-loaded, followed by input modes, then cost, route and payment gating. Nothing is padded, though the middle sentence crams three distinct modes into one dense clause.

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 zero-required-parameter tool with 17 fields, nested objects, no annotations and no output schema, the description is far too thin. It never explains how the calculation inputs are assembled, which fields matter versus which are suite-wide boilerplate, or what the caller receives back.

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 17 parameters, so the description must compensate and largely does not. It sheds light only on three concepts (activities, factors, carbonIntensity), leaving csv/json/text/file/files, permits, reports, suppliers, waterRecords, wasteManifests, asOf, expiryWarningDays and consistencyToleranceKg entirely unexplained, including whether they are even relevant to a Scope 2 calculation.

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 and resource ("Calculate Scope 2 emissions") and enumerates the accepted input paths: caller-supplied electricity activities/factors, disclosed public-style grid factors, or the optional Carbon Intensity API. Scope 2 is inherently distinguishable from the Scope 1 and Scope 3 siblings, though the description never names or contrasts them.

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?

The enumeration of input paths implies when each mode applies (own factors vs. built-in grid factors vs. the key-free API), which is more than nothing. There are no explicit when-not conditions, no guidance on choosing between the caller-factor path and the API path, and no mention of prerequisites or how the mode is selected in the payload.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources