Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Normalize carbon emission factors

environmental-intelligence_carbon-emission-factor-normalize

Normalize caller-supplied emission factors with source, version, and asOf provenance. Disclosed public-style DEFRA/eGRID references may be listed when no factors are supplied. No paid ESG database. Price $0.03 USDC. POST /api/v1/environmental-intelligence/carbon-emission-factor-normalize. 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_carbon-emission-factor-normalize"
  }
}

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 must carry the behavioral burden. It usefully discloses pricing ($0.03 USDC), unpaid-call behavior (HTTP 402 and no execution), no paid ESG database, and fallback public references when no factors are supplied, but it does not explain whether the operation is read-only, what normalization produces, or whether any data is stored or mutated.

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 description is short and front-loads the core normalization purpose before operational details such as public references, pricing, endpoint, and unpaid-call behavior. The sentences are lean, though the endpoint and pricing details make it slightly more operational than descriptive.

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 high-complexity tool with 17 optional parameters, nested objects, no annotations, no output schema, and 0% schema description coverage. The description covers the core factors case and billing behavior but leaves most input branches and the return shape unexplained, which is not enough for correct invocation beyond a simple factors-only call.

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, including nested objects and several unrelated data arrays. The description adds some meaning for factors, source, version, and asOf, but it does not explain csv, file, json, text, files, permits, reports, suppliers, activities, waterRecords, wasteManifests, carbonIntensity, or the other exposed parameters.

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 states a specific verb and resource: normalize caller-supplied emission factors with source, version, and asOf provenance. It is distinguishable from sibling calculation and validation tools by its focus on factor normalization, though it does not explicitly name an alternative.

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 description implies usage by saying factors are caller-supplied and that public-style DEFRA/eGRID references may be listed when no factors are supplied. It does not explicitly state when to choose this tool versus sibling scope calculation or validation tools, nor does it provide exclusions.

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