Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Calculate Scope 1 emissions

environmental-intelligence_scope-1-emissions-calculate

Calculate Scope 1 emissions from caller-supplied activity quantities and emission factors (or disclosed public-style factors when unmatched). Factor source, version, and asOf are echoed. Price $0.04 USDC. POST /api/v1/environmental-intelligence/scope-1-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-1-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
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 unusually well: it discloses the $0.04 USDC price, the 402 payment gate ('Unpaid calls return 402 and do not run'), the unmatched-factor fallback, and that factor source, version, and asOf are echoed back. It stops short of stating whether the operation is read-only or idempotent, or what the computed result contains beyond the echoed factor metadata.

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?

The purpose is front-loaded in the first clause, followed by the factor-echo behavior and then commercial/transport facts. Nearly every sentence earns its place, though the raw POST path is partly redundant with the name and could be trimmed.

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?

This is a 17-parameter, nested-object tool with no annotations and no output schema, yet the description explains almost none of the input surface or the shape of the result. It answers the payment and factor-sourcing questions well but leaves an agent unable to decide which of the many optional inputs (files vs. csv vs. json, permits, suppliers, water/waste records) are actually consumed by the Scope 1 calculation.

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 it only explains two concepts (activities and factors) plus asOf. Fifteen parameters — csv, text, json, file, files, permits, reports, suppliers, waterRecords, wasteManifests, carbonIntensity, expiryWarningDays, consistencyToleranceKg — receive no explanation of purpose or interaction.

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 names a specific verb and resource: 'Calculate Scope 1 emissions' from caller-supplied activity quantities and emission factors. The 'Scope 1' qualifier is enough to separate it from environmental-intelligence_scope-2-emissions-calculate without opening a schema, though the sibling is never named explicitly.

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 alternative tool is named. The fallback clause about 'disclosed public-style factors when unmatched' hints at an internal behavior but does not tell an agent when this tool is the right choice over the scope-2 or factor-normalize siblings.

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